[rabbitmq-discuss] STOMP Frame
tonyg at lshift.net
Tue Feb 17 14:48:26 GMT 2009
Dan Di Spaltro wrote:
> I noticed that at the end of the STOMP frame you only have a null
> character when the reference implementation looks to have a null
> followed by a \n character. Am I misinterpreting this, because the
> documentation doesn't seem to say anything about a null followed by a
> return. Is this an issue for anyone else?
IMO the wording in the protocol spec http://stomp.codehaus.org/Protocol
could be tightened, but implies that a newline after the nul is an
error. And personally, I think a newline after a nul is nonsensical and
should be an error.
I don't know how to fix this properly: ignore the spec, and supply a
newline? Try to get the other implementations changed? Get the spec changed?
 Tony Garnock-Jones | Mob: +44 (0)7905 974 211
 LShift Ltd | Tel: +44 (0)20 7729 7060
  http://www.lshift.net/ | Email: tonyg at lshift.net
More information about the rabbitmq-discuss