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
This is just a note, how dangerous this setting is. The default class should be ByteArray. The developer then has to decide, if this is really a ByteArray (e.g. for an image) or it may be an UTF8 string or an CodePage string.
So far I have never come across this problem and I found the .NET binding very boring to handle all this ByteArray (from/back UTF8) and my data structure avoided german umlauts. But now I understand, that the .NET binding is useful.
Perhaps the developer must ask some header information before retrieving the body ... and do not trust, that the developer set the mime type right.
The text was updated successfully, but these errors were encountered:
So, one programming style can be, that - if you always get the same kind of object - you may define an instance of
GsAmqEnvelope (and reuse this instance) and calls messageBodyClass: with the class in mind.
This is just a note, how dangerous this setting is. The default class should be ByteArray. The developer then has to decide, if this is really a ByteArray (e.g. for an image) or it may be an UTF8 string or an CodePage string.
So far I have never come across this problem and I found the .NET binding very boring to handle all this ByteArray (from/back UTF8) and my data structure avoided german umlauts. But now I understand, that the .NET binding is useful.
Perhaps the developer must ask some header information before retrieving the body ... and do not trust, that the developer set the mime type right.
The text was updated successfully, but these errors were encountered: