quickfix-developers

[Quickfix-developers] [qfj] Queueing messages before Logged on?

[Brad H. <Bra...@gb...>]

Hi All,

I would like to be able to send messages to quickfixj after a session
has been created but while it is not logged on, and then have those
messages sent automatically once the session is logged on.  Is this
something that is currently possible? =20

Some additional background info may be in order.  Our counterparty fix
engine is really just a wrapper for another system, and before we start
sending orders etc we have to login to the other system with a BE User
request.  No, I'm not sure why they didn't just add some custom fields
to the normal fix login message. =20

We wanted to ensure that no "normal" messages could be sent before the
BE User request.  To do this we have modified Session to only consider
itself fully logged on after the BE User request, and to automatically
send the BE after the normal fix logon.  Before our application sends
any messages it waits for session.isLoggedOn() to be true.  I'm not
really happy with this - I'd prefer it to be able to just send it and
let quickfix take care of sending when it can, hence the original
question.

I'm also interested in hearing of better ways to do the BE User request
thing - I'd really prefer not to maintain our own changes in Session.
We're quite happy to contribute the changes if they'd be useful to the
quickfixj community, but at the moment it isn't optional so would
require a little work.

Regards,
Brad.

Re: [Quickfix-developers] [qfj] Queueing messages before Logged on?

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

You can send messages at any time.  There is no need to wait for a 
succesful logon.  The messages will be queued sent automatically after 
the next succesfull connection.

--oren

Brad Harvey wrote:

> Hi All,
>
> I would like to be able to send messages to quickfixj after a session 
> has been created but while it is not logged on, and then have those 
> messages sent automatically once the session is logged on.  Is this 
> something that is currently possible? 
>
> Some additional background info may be in order.  Our counterparty fix 
> engine is really just a wrapper for another system, and before we 
> start sending orders etc we have to login to the other system with a 
> BE User request.  No, I'm not sure why they didn't just add some 
> custom fields to the normal fix login message. 
>
> We wanted to ensure that no "normal" messages could be sent before the 
> BE User request.  To do this we have modified Session to only consider 
> itself fully logged on after the BE User request, and to automatically 
> send the BE after the normal fix logon.  Before our application sends 
> any messages it waits for session.isLoggedOn() to be true.  I'm not 
> really happy with this - I'd prefer it to be able to just send it and 
> let quickfix take care of sending when it can, hence the original 
> question.
>
> I'm also interested in hearing of better ways to do the BE User 
> request thing - I'd really prefer not to maintain our own changes in 
> Session.  We're quite happy to contribute the changes if they'd be 
> useful to the quickfixj community, but at the moment it isn't optional 
> so would require a little work.
>
> Regards,
> Brad.
>