You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I think I found a little bug with the publication and read of the messages when non-Json content is provided for the message content while trying to do a simple test by just sending a string (which is still technically JSON). For example,
producer.PostPublication(ServerUrl, SessionID, Topic, "\"A test message\"");
Basically, if non-Json content is used it is not written nor read properly.
I assume this is based on the assumption that the content should be a JSON Object and/or the way the JSON library in use handles non-Json content.
Suggested short term fix would be to raise an exception if a non-Json Object is provided or being read, just so that it is clear to the user of the library that it is expected to be a JSON Object.
Long term fix of course would be to support the different content types.
The text was updated successfully, but these errors were encountered:
Hello,
I think I found a little bug with the publication and read of the messages when non-Json content is provided for the message content while trying to do a simple test by just sending a string (which is still technically JSON). For example,
Basically, if non-Json content is used it is not written nor read properly.
I assume this is based on the assumption that the content should be a JSON Object and/or the way the JSON library in use handles non-Json content.
Suggested short term fix would be to raise an exception if a non-Json Object is provided or being read, just so that it is clear to the user of the library that it is expected to be a JSON Object.
Long term fix of course would be to support the different content types.
The text was updated successfully, but these errors were encountered: