[Quickfix-developers] QuickFIX 1.10.2 is now available

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

QuickFIX 1.10.2 is now available at http://www.quickfixengine.org/

A couple of point releases went out before I had a chance to announce  
1.10.0.  You can get the release notes for all versions here: http:// 
www.quickfixengine.org/NEWS

Well now.  It's been a bit longer between releases then normal, but  
here it is.  Not everything we wanted to get in here did, but we will  
be pushing for a 2.0 release and hope to incorporate some of our more  
ambitious goals.

Some of the things you will find in this version is automated support  
for SequenceResets.  If your engine receives one, it will reset your  
sequence numbers and send the appropriate ack.  If you attach a  
ResetSeqNumFlag=Y to your logon message, the engine will reset its  
sequence numbers appropriately.  This flag will also automatically  
attach itself at the appropriate time if you have ResetOnDisconnect  
or ResetOnLogoff set.

You can now reliably stop and start initiators and acceptors as much  
as you like.  Previously once you stopped in initiator or acceptor,  
it wasn't designed to be brought back up and you'd have to throw it  
away.  Now you can call start/stop as much as you like.  Even better,  
the initiator/acceptor will attempt to properly logout of all  
sessions before shutting down.  It will only forcibly take down a  
session if it doesn't respond withing 5 seconds to the logout attempt.

Some things with field validation.  You can turn them off for user  
defined fields with the ValidateUserDefinedFields configuration  
setting.  Also the validation algorithm will now check for required  
fields in the header, trailer, and repeating groups instead of just  
the main message body.

The much wanted method to getSessions from an initiator/acceptor is  
now available in all APIs.

And you can check the release notes for all the details.  Did we miss  
something?  Please enter it into the bugtracker (http:// 
www.quickfixengine.org/bugtracker/).  That's the best way to ensure  
that we don't miss it.  The mailing list has grown a bit much to be  
used as a way to reliably track such things (the developer list alone  
had 190 posts last month).  After reporting something to the list, if  
the discussion reveals a need for action, please help us out by  
entering it into the bugtracker and attaching any relevant log files.

--oren