Re: [Quickfix-developers] Lost Messages?

[<Nil...@co...>]

Yes - Message Resend/ Gapfill, is taken care by the QF. You don't need
to worry about it.=0D

However, it would be good to know if someone can throw some light on,
How to simulate the packet/message drop in test environment.

Regards
-nilesh

>-----Original Message-----
>From: qui...@li...
[mailto:quickfix-
>dev...@li...] On Behalf Of azmat
>Sent: Friday, January 25, 2008 12:28 PM
>To: qui...@li...
>Subject: [Quickfix-developers] Lost Messages?
>
>QuickFIX Documentation:
>http://www.quickfixengine.org/quickfix/doc/html/index.html
>QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>All,
>
>I have another concern, and I couldn't find the answer to it anywhere
in
>the
>forums.  I'm sure its probably a simple question to answer but I just
don't
>know it :-)
>
>What happens when I send a message to a FIX Server (from my own FIX
client)
>and somehow the message is dropped or lost.  Does QF store the messages
in
>some sort of queue where it can resend the messages or is this
something I
>will need to write?  I believe according to the the FIX spec there are
many
>requirements for FIX engines and how they are supposed to handle these
>scenarios with gapfill procedures.      I was wondering how this is
handled
>by QF.  Any help would be much appreciated!
>
>thanks!
>Azmat
>--
>View this message in context: http://www.nabble.com/Lost-Messages--
>tp15082077p15082077.html
>Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
>
>
>-----------------------------------------------------------------------
--
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Quickfix-developers mailing list
>Qui...@li...
>https://lists.sourceforge.net/lists/listinfo/quickfix-developers

This e-mail and any files transmitted with it are for the sole use of the=
 intended recipient(s) and may contain confidential and privileged=
 information.
If you are not the intended recipient, please contact the sender by reply=
 e-mail and destroy all copies of the original message.=0D
Any unauthorised review, use, disclosure, dissemination, forwarding,=
 printing or copying of this email or any action taken in reliance on this=
 e-mail is strictly=0D
prohibited and may be unlawful.