Re: [Quickfix-developers] Acceptor and fork

[Djalma R. d. S. F. <drs...@gm...>]

Shared memory and a mutex can be used to replace the static data.

I agree that the fork approach would bring more robustness to the FIX Engine
and the application, but probably with lower performance due to the IPC
requirements to synchronize data within the sessions. The multi-threading
approach should be much faster; the robustness can be achieved with suitable
error handling in the application.

Djalma Santos Filho

On 1/15/07, Caleb Epstein <cal...@gm...> wrote:
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> On 1/15/07, Ste...@de... > However, I have a
> UNIX environment and I want to use something like
> > following code example.
> > Anyone knows if there is a way or better a sample to do this with QF.
> > I think it is a new acceptor implementation.
> >
> > [ snip code using fork ]
>
> I think this would have to be a new Acceptor implementation.  It ought
> to work fine, but you'd be faced with the problem that you could not
> detect duplicate connections to the same session.  The threaded
> approach allows static data structures to be shared across all
> sessions, so the Acceptor can determine if a second client tries to
> login using the same credentials as another, currently-active session.
> With this forked approach, you'd need to use some other technique
> (file locking perhaps) to provide this safeguard.
>
> --
> Caleb Epstein
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>