[Quickfix-developers] RE: QuickFIX for Python

[Shawn Y. <sya...@ge...>]

Sounds good to me, thanks.  This exchange (CME) is touchy so I'm glad =
you found a good solution.


Shawn Yarbrough
Senior E-Trading Developer
Gelber Group, LLC
sya...@ge...


THE MESSAGES AND DOCUMENTS TRANSMITTED WITH THIS NOTICE CONTAIN =
CONFIDENTIAL INFORMATION BELONGING TO THE SENDER. IF YOU ARE NOT THE =
INTENDED RECIPIENT OF THIS INFORMATION, YOU ARE HEREBY NOTIFIED THAT ANY =
DISCLOSURE, COPYING, DISTRIBUTION OR USE OF THE INFORMATION IS STRICTLY =
PROHIBITED. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE =
NOTIFY THE SENDER IMMEDIATELY.




-----Original Message-----
From: Oren Miller [mailto:or...@qu...]
Sent: Friday, April 07, 2006 12:08 PM
To: Shawn Yarbrough
Cc: qui...@li...
Subject: Re: QuickFIX for Python


I checked in a fix that makes sure the SendingTime and =20
OrigSendingTime will match for SequenceReset messages.  The resend =20
functionality is different because there the timestamps can and =20
should be different, but for SequenceResets, the message is being =20
sent for the first time.  The only reason there is an OrigSendingTime =20
in the message is that it must accompany and message containing a =20
PossDup field.  And the only reason it has a PossDup field is because =20
any message sent as a result of a resend request must contain a =20
PossDup field, even if the message was never sent before.  So it is a =20
bit of an anomoly.

--oren