Re: [Quickfix-developers] Starting and Stopping Individual Sessions

[Oren M. <or...@qu...>]

Paul,

You can control this with the logon/logoff methods on the session  
object.  In this way you can control whether you would like a session  
to logon, or stay logged off during holidays.

Also, session times can be set on a per session basis, not a per  
initiator basis.  As long as you place the session time in the  
SESSION section instead of the DEFAULT section, you can have a  
different session time for each session even while running within the  
same initiator.

--oren

On Nov 13, 2006, at 8:48 AM, PaulVR wrote:

> Our current implementation has one initiator per session (one  
> initiator
> manages one session and there are as many initiators as there are  
> sessions).
> According to QuickFIX documentation, one initiator can manage as many
> sessions as is required and I presume that having one initiator  
> manage all
> sessions is the preferred approach; we seem to have problems on  
> termination
> when sessions take too long to close, even though we call initiator's
> close() method with 'force' set to 'true': ...->close(true).
>
> I was considering changing this and using one initiator instead of  
> many but
> there is one thing I am not too sure as to how to handle, and this is
> opening and closing of sessions. Naturally QuickFIX engine handles  
> their
> working hours and it is even possible to specify their working days  
> but it
> does not handle holidays and, since it lives in GMT, I am not too  
> sure how
> it would handle sessions with sufficiently different time zones
> (hypothetically, what will happen if the time zone is 9 hours ahead  
> of GMT
> and opening time is 8:00 GMT). Our current implementation starts/ 
> stops the
> initiator which will start/stop the session it manages but I could  
> not find
> a mechanism that would allow me to micro-manage sessions in this  
> way if they
> are all managed by the same initiator.
>
> Thank you.
>
> Paul