Re: [Quickfix-developers] Queuing messages

[Alan K. <ala...@gm...>]

I am running a quickfix app that basically does routing. It receives a FIX
mssage on session A, does some processing, then sends it to session B. How
do I safestore any message destined for B when B is not connected? In the
event the quickfix app crashes in the interim these safestored messages
should persist.


On Thu, Oct 4, 2012 at 10:54 AM, Mikhail Veygman <mve...@gm...> wrote:

> Not quite sure I understand the query.
>
> The issue you're facing seems to be one of reliable storage medium like
> fully redundant disk storage or DB clusters or similar. Or is your question
> about something else?
> On Oct 4, 2012 9:39 AM, "Alan Kurlansky" <ala...@gm...> wrote:
>
>> QuickFIX Documentation:
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>>
>> What would be the recommended way to save/persist FIX messages that
>> cannot at the moment be sent because the destination session is not
>> connected? I want to guarantee that the message would even persist in the
>> event of a crash/restart. Researching this I see a number of possibilities
>> but wanted to see if I am missing a very simple solution to this. Thanks
>>
>>
>> ------------------------------------------------------------------------------
>> Don't let slow site performance ruin your business. Deploy New Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-dev2dev
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>
>


-- 
Al Kurlansky
215-778-8173 cell