[Quickfix-developers] Processing messages in batches

[jgoodman999 <jef...@cm...>]

I have an application right now that has a class that implements Application
to process all the messages.  It processes one message at a time, stores in
our database and sends events to the user's front end of the change.  The
problem is that if I have hundreds of messages at once coming in, then I am
sending notifications very quickly and its slowing the front end down.  I
would like to read a message, insert, read a message, insert, etc until I
receive 50 messages or so, then commit and send all events at once.  The
problem is once I am done processing one message and return, it is gone so
if the server crashes somewhere before 50, The messages that have not been
committed will be gone and wont be resent on startup.  Any suggestions. 
Also, It seems that Quickfix must be single threaded since we must process
the messages in the order they arrive, correct?  So what benefit does the
multithreaded socket have?
-- 
View this message in context: http://www.nabble.com/Processing-messages-in-batches-tf4679528.html#a13370932
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.