Hi Dejan!
Thank you for explanation, now it seems clear to me.
--
View this message in context:
http://www.nabble.com/Stomp-and-content-length-tp22960715p22969783.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ent's one? Please clarify :)
> --
> View this message in context:
> http://www.nabble.com/Stomp-and-content-length-tp22960715p22966128.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
arify :)
--
View this message in context:
http://www.nabble.com/Stomp-and-content-length-tp22960715p22966128.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
so in Ruby: text can be sent in
UTF-8 or other Unicode encodings and it will contain NULL bytes that are
designed to be a Stomp message end. So it seems ActiveMQ should be fixed :)
--
View this message in context:
http://www.nabble.com/Stomp-and-content-length-tp22960715p22960784.html
Sent from the
f implementing one more condition checking if message's
'content-type' is 'text/plain'?
Thank you in advance.
--
View this message in context:
http://www.nabble.com/Stomp-and-content-length-tp22960715p22960715.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.