[beep4j-user] Suppressing the Content-Type header

[Thomson, M. <Mar...@an...>]

BEEP defines a default value for the content type header.  beep4j
doesn't take advantage of this, and always provides a content-type
header.

I have a attached a small patch for MessageHeader.java that enables the
suppression of the content-type header when sending messages.  With the
patch, the content-type header is not set unless explicitly set.  When
receiving a message, it reports application/octet-stream to the
application if the header is missing.

It's a fairly trivial thing, and you might say that bit misers should
not be using text-based protocols, but it does halve the overhead for
each message.

Cheers,
Martin 

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]