Re: [Quickfix-developers] controlling quickFix engine
Brought to you by:
orenmnero
From: Oren M. <or...@qu...> - 2004-12-09 14:47:06
|
For connect/disconnect there are the Session::logon() and Session::logout() methods. There is Session::reset(), Session::setNextSenderMsgSeqNum(), and Session::setNextTargetMsgSeqNum(). TestRequest and ResendRequest messages can be sent using sendToTarget(). Not sure what you mean by end of day. These are all public methods, at least in the most current version: http://www.quickfixengine.org/quickfix/doc/html/ class_f_i_x_1_1_session.html --oren On Dec 9, 2004, at 7:39 AM, Michael Raykh wrote: > Looking for a way to monitor and control QF for our support desk. Need > to do things like disconnect, > reset, reset seq number, test request, resend request, end-of-day. > Seems that the functionality needed exists but more often than not > it's private methods in Session, SessionState... > > - is this correct? > - seems that something like this might be pretty common need- would it > make sense to provide neccessary "hooks"? > > Michael > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. This message contains confidential information and > is intended only for the individual named. If you are not the named > addressee you should not disseminate, distribute or copy this e-mail. |