[Vortex] Are content-types and transfer-encodings supposed to work?

[Sam Roberts]

On Tue, May 13, 2008 at 4:08 PM, Chris Yourch <chris at replicus.com> wrote:
> Ahhhhhh.... the mutant vortex protocols are attacking....    :)
>
>  Sorry, I couldn't resist.

Who knows, mutant may be more common!

Beepy had the same misinterpretation of the spec.

beep4j was using a "MIME" format that involved "=" instead of ":" for
field specifications (oops! fixed, now), but I don't recall if it had
the misinterpretation under question.

Anyhow, its not so easy to change. At least, a connection specific
flag that triggers correct behaviour would be nice.

If the first frame in a message is parseable as MIME, maybe it should be treated
as such and the headers seperated from the message data. If not
parseable, maybe assume it was encoded without the required MIME
headers, and use entire frame as message data.

This would interop reasonably, unless somebody happened to be sending
messages that look like MIME, AND didn't put an empty MIME header
section...

Cheers,
Sam