{{Quickfixn}} Can be message store given a shared path

[Sumit Gupta (SUGU)]

Hi Mike,

Thank you for your quick reply.

As our service is critical and lot of fix traffic it handles. You can imagine that in 2.5 days  one of the fix store (for a client) goes upto 3 gb.
I am not sure if shared path implementation will introduce latency to fix messages delivery.

Could you/anyone put some light here, if anyone is already using shared path for message store.

And also why RefreshOnLogon=y while reconnecting on passive to active server?

Thank you
Sumit
From: Mike Gatny <mgatny at connamara.com<mailto:mgatny at connamara.com>>
Date: Tuesday, 02 Oct 2018, 7:53 PM
To: Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com<mailto:quickfixn at lists.quickfixn.com>>
Subject: Re: {{Quickfixn}} Can be message store given a shared path

On Tue, Oct 2, 2018 at 9:52 AM Sumit Gupta (SUGU) <SUGU at saxobank.com<mailto:SUGU at saxobank.com>> wrote:
I could see one resolution:
1. If I mention the message store path as shared path. ( i am not sure if this is a practical resolution).

Yes, do this, and use RefreshOnLogon=Y.  This setting causes the store files to be re-read when clients logon to the Passive.

Another solution is to use a datatbase-backed implementation of IMessageStore.  QuickFIX/n does not currently include one, but you could implement one fairly easily.

--
Mike Gatny
Connamara Systems

This email may contain confidential and/or privileged information. If you are not the intended recipient - or have received this email by mistake - please notify the sender immediately and destroy the email. Any unauthorised copying, disclosure and/or distribution of the contents and/or attachments in this email is strictly prohibited.

Email transmission security and error-free delivery cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete and/or contain malware (virus). The sender of this email, therefore, does not accept liability for any errors and/or omissions in the contents of this message, which may arise as a result of email transmission.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20181002/1e3f257c/attachment.htm>