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

[Jie Zhu]

You may also be able to use a Log4netLog class something like:

   public class Log4netLog:ILog
    {
        private static readonly log4net.ILog log = log4net.LogManager.GetLogger("Fix");

        public Log4netLog()
        {
        }

        public void OnIncoming(String text)
        {
            log.InfoFormat("onIncoming: {0}", text);
        }

        public void OnOutgoing(String text)
        {
            log.InfoFormat("onOutgoing: {0}", text);
        }

        public void OnEvent(String text)
        {
            log.InfoFormat("onEvent: {0}", text);
        }

        public void Clear()
        {
        }


        public void Dispose()
        {
           // throw new NotImplementedException();
        }
}


When do log4net settings, you can use AdonetAppender or RollingfileAppender to limit the size.


From: Quickfixn [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Mike Gatny
Sent: Tuesday, October 02, 2018 10:25 AM
To: Mailing list for QuickFIX/n
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 and any attached files are confidential and may be legally privileged. If you are not the intended recipient, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this email. Email transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore is in no way liable for any errors or omissions in the contents of this message which may arise as a result of email transmission. If verification is required please request a hard copy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20181002/07bfc79e/attachment.htm>