The Send STOMP RFC example

[jgauffin]

In the RFC the following example exists:

SEND
destination:/queue/a
receipt:message-12345

hello queue a^@

Ins't the Content-Length header required when there is a body?

[Jason Briggs]

It’s not mandatory:

SEND frames SHOULD include a content-length header and a content-type header if a body is present.

--
You received this message because you are subscribed to the Google Groups "stomp-spec" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stomp-spec+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[jgauffin]

A body was included in that message.

[Hiram Chirino]

Correct. But it's still not an invalid STOMP message since the header
is not required.

--
Hiram Chirino

Engineering | Red Hat, Inc.

hchi...@redhat.com | fusesource.com | redhat.com

skype: hiramchirino | twitter: @hiramchirino

blog: Hiram Chirino's Bit Mojo

[jgauffin]

I don't understand.

The specification states "SEND frames SHOULD include a content-length header and a content-type header if a body is present".

And since the message do have a body, how can it not be invalid?

[Jason Briggs]

SHOULD is different from MUST.  In other words, the content-length and content-type headers are not absolutely required.

[Jason Briggs]

PS.  Reading this might help clarify:  http://en.wikipedia.org/wiki/MoSCoW_Method