Re: [Quickfix-developers] Persisting unprocessed messages

[Simeon S. <sim...@gm...>]

Thanks Viktor,

I imagine this is a common problem that one needs to guard against. What is
the common solution? One way would be to take messages from quickfix with
minimal processing and persist them at application level then process them
in a separate thread/process - this offloads persisting responsibilities to
the application. Another way would be to persist the SeqNum of the last
processed message and then at login request from the acceptor all messages
after this. However, I will be relying on the acceptor supporting this
functionality (i.e. keeping a history of messages).

Do these methods sound like a reasonable way to deal with this?


On 23 May 2016 at 18:36, Viktor Pogrebnyak <pohrebnyak@i.ua> wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/
>
> Hi,
>
> Quickfix extracts/processes messages from network buffer one-by-one and
> writes them to the disk if configured. There is no way to force behavior
> you
> want in the current engine.
>
> Cheers,
> Viktor
>
>
>
> --
> View this message in context:
> http://quickfix.13857.n7.nabble.com/Persisting-unprocessed-messages-tp6807p6808.html
> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>