[Quickfix-developers] 'Supposed' QF Behaviour

[Vitor C. <vc...@hi...>]

Hello to all,
 
I've been using QF for some time now, at the moment I'm using QF 1.6.0,
but recently I've come across a behaviour from QF that I wasn't
expecting and I can't understand how I've never found it before:
I'm developing an Initiator application (more specifically a Windows
service Initiator, using ThreadedSocketInitiator) that I wanted to start
automatically on boot time and have QF start the session/s whenever the
start time for the session/s came. And I thought that QF did this. But
to my surprise I found that if I started the initiator before the
session/s start time, that/those session/s would never start.
Furthermore, I found that after the session/s end time the initiator
would disconnect from the other side, but remained trying to connect
every ReconnectInterval.
Because of this I have to make sure of two things: first I must start
the initiator after all the sessions StartTime has passed and second if
I don't want the Eventlog to became full of failed connection attempts I
must stop the initiator after the EndTime of all the sessions has
passed.
Although this isn't quite easy to accomplish I feel I'm missing
something here.
 
Can anyone clarify these issues? Is this the expected behaviour of this
version of QF? Did any of these changed from the previous versions?
 
Thanks in advance
 
 

Vitor Castro | DIS
<mailto:vc...@hi...>