Re: [Quickfix-developers] Field with embedded null character

[Oren M. <or...@qu...>]

I added some unit tests and it seems to work except for one problem.  I 
have a message that I'm passing into the messages constructor, which is 
just a normal message.  The checksum of this message is 218.  The test 
is that I send the same message in except I added a null character at 
the end of one of the fields.  It is able to parse everything fine, but 
it determines that the checksum of the message with the null should be 
219 and throws an Invalid message.  Now since null has a value of 0 I 
would expect that the checksum of these two messages should be 
identical.  Anybody see any flaw in this reasoning?

--oren

On Oct 29, 2004, at 9:37 AM, Caleb Epstein wrote:

> Attached is a comprehensive patch to QuickFIX 1.9.2 with the necessary
> changes to Field.h, Parser.cpp and ThreadedSocketConnector.{cpp,h} to
> deal with NUL bytes in messages.
>
> Clearly this must be a pretty uncommon need, otherwise it would have
> been raised on this list before, but if anyone plans on using
> encrypted messages or moving around messages with binary Data fields,
> this patch would be a big win.
>
> -- 
> Caleb Epstein
> cal...@gm...
> <quickfix-1.9.2-allow-nuls.diff>