Thread: [Quickfix-users] error:no session defined for initiator
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-users
|
From: George M. C. <ge...@qu...> - 2005-04-12 13:17:48
|
I am trying to use the sample c# application code with a simple config
file. I get the error "no session defined for initiator" in the
constructor of my Intiator object. Here is my code and the config fiel
contents:
try
{
SessionSettings settings = new
SessionSettings(_fileName);
FixApplication application = new FixApplication();
FileStoreFactory storeFactory = new
FileStoreFactory(settings);
FileLogFactory logFactory = new
FileLogFactory(settings);
MessageFactory messageFactory = new
DefaultMessageFactory();
ThreadedSocketInitiator init = new
ThreadedSocketInitiator( application, storeFactory, settings,
messageFactory );
}
catch(ConfigError e)
{
log.Error( e );
}
config file:
[DEFAULT]
ConnectionType=initator
ReconnectInterval=30
HeartBtInt=30
SenderCompID=A
[SESSION]
BeginString=FIX.4.2
TargetCompID=B
SocketConnectPort=9890
SocketConnectHost=192.168.1.8
DataDictionary=C:/tools/quickfix/quickfix-bin-vc7-1.9.4/quickfix/spec/FIX42.xml
|
|
From: Guillermo A. A. <gar...@vi...> - 2005-04-13 14:00:15
|
CkhhdmUgeW91IGp1c3QgY29waWVkIHRoZSBjb250ZW50cyBvZiB5b3VyIGNvbmZpZyBmaWxlIGhl cmU/IElmIHRoYXQncyB0aGUKY2FzZSB5b3Ugc2hvdWxkIGxvb2sgY2FyZWZ1bGx5IHRvIHRoZSBD b25uZWN0aW9uVHlwZSBmaWVsZDogaXQgc2hvdWxkIGJlCiJpbml0aWF0b3IiIGluc3RlYWQgb2Yg ImluaXRhdG9yIi4KCkhvcGUgaXQgd2lsbCBoZWxwLgoKQ2hlZXJzLApHdWlsbGVybW8uCgotLS0t LU1lbnNhamUgb3JpZ2luYWwtLS0tLQpEZTogcXVpY2tmaXgtdXNlcnMtYWRtaW5AbGlzdHMuc291 cmNlZm9yZ2UubmV0ClttYWlsdG86cXVpY2tmaXgtdXNlcnMtYWRtaW5AbGlzdHMuc291cmNlZm9y Z2UubmV0XUVuIG5vbWJyZSBkZSBHZW9yZ2UKTS4gQ29sZXMKRW52aWFkbyBlbDogbWFydGVzLCAx MiBkZSBhYnJpbCBkZSAyMDA1IDE1OjE4ClBhcmE6IHF1aWNrZml4LXVzZXJzQGxpc3RzLnNvdXJj ZWZvcmdlLm5ldApBc3VudG86IFtRdWlja2ZpeC11c2Vyc10gZXJyb3I6bm8gc2Vzc2lvbiBkZWZp bmVkIGZvciBpbml0aWF0b3IKCgpRdWlja0ZJWCBEb2N1bWVudGF0aW9uOgpodHRwOi8vd3d3LnF1 aWNrZml4ZW5naW5lLm9yZy9xdWlja2ZpeC9kb2MvaHRtbC9pbmRleC5odG1sClF1aWNrRklYIEZB UTogaHR0cDovL3d3dy5xdWlja2ZpeGVuZ2luZS5vcmcvd2lraWZpeC9pbmRleC5waHA/UXVpY2tG aXhGQVEKUXVpY2tGSVggU3VwcG9ydDogaHR0cDovL3d3dy5xdWlja2ZpeGVuZ2luZS5vcmcvc2Vy dmljZXMuaHRtbAoKSSBhbSB0cnlpbmcgdG8gdXNlIHRoZSBzYW1wbGUgYyMgYXBwbGljYXRpb24g Y29kZSB3aXRoIGEgc2ltcGxlIGNvbmZpZwpmaWxlLiBJIGdldCB0aGUgZXJyb3IgIm5vIHNlc3Np b24gZGVmaW5lZCBmb3IgaW5pdGlhdG9yIiBpbiB0aGUKY29uc3RydWN0b3Igb2YgbXkgSW50aWF0 b3Igb2JqZWN0LiBIZXJlIGlzIG15IGNvZGUgYW5kIHRoZSBjb25maWcgZmllbApjb250ZW50czoK CnRyeQogICAgICAgICAgICAgICAgewogICAgICAgICAgICAgICAgICAgIFNlc3Npb25TZXR0aW5n cyBzZXR0aW5ncyA9IG5ldwpTZXNzaW9uU2V0dGluZ3MoX2ZpbGVOYW1lKTsKICAgICAgICAgICAg ICAgICAgICBGaXhBcHBsaWNhdGlvbiBhcHBsaWNhdGlvbiA9IG5ldyBGaXhBcHBsaWNhdGlvbigp OwogICAgICAgICAgICAgICAgICAgIEZpbGVTdG9yZUZhY3Rvcnkgc3RvcmVGYWN0b3J5ID0gbmV3 CkZpbGVTdG9yZUZhY3Rvcnkoc2V0dGluZ3MpOwogICAgICAgICAgICAgICAgICAgIEZpbGVMb2dG YWN0b3J5IGxvZ0ZhY3RvcnkgPSBuZXcKRmlsZUxvZ0ZhY3Rvcnkoc2V0dGluZ3MpOwogICAgICAg ICAgICAgICAgICAgIE1lc3NhZ2VGYWN0b3J5IG1lc3NhZ2VGYWN0b3J5ID0gbmV3CkRlZmF1bHRN ZXNzYWdlRmFjdG9yeSgpOwogICAgICAgICAgICAgICAgICAgIFRocmVhZGVkU29ja2V0SW5pdGlh dG9yIGluaXQgPSBuZXcKVGhyZWFkZWRTb2NrZXRJbml0aWF0b3IoIGFwcGxpY2F0aW9uLCBzdG9y ZUZhY3RvcnksIHNldHRpbmdzLAptZXNzYWdlRmFjdG9yeSApOwogICAgICAgICAgICAgICAgfQog ICAgICAgICAgICAgICAgY2F0Y2goQ29uZmlnRXJyb3IgZSkKICAgICAgICAgICAgICAgIHsKICAg ICAgICAgICAgICAgICAgICBsb2cuRXJyb3IoIGUgKTsKICAgICAgICAgICAgICAgIH0KCmNvbmZp ZyBmaWxlOgpbREVGQVVMVF0KQ29ubmVjdGlvblR5cGU9aW5pdGF0b3IKUmVjb25uZWN0SW50ZXJ2 YWw9MzAKSGVhcnRCdEludD0zMApTZW5kZXJDb21wSUQ9QQoKW1NFU1NJT05dCkJlZ2luU3RyaW5n PUZJWC40LjIKVGFyZ2V0Q29tcElEPUIKU29ja2V0Q29ubmVjdFBvcnQ9OTg5MApTb2NrZXRDb25u ZWN0SG9zdD0xOTIuMTY4LjEuOApEYXRhRGljdGlvbmFyeT1DOi90b29scy9xdWlja2ZpeC9xdWlj a2ZpeC1iaW4tdmM3LTEuOS40L3F1aWNrZml4L3NwZWMvRklYNDIuCnhtbAoKCgotLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClNGIGVtYWlsIGlz IHNwb25zb3JlZCBieSAtIFRoZSBJVCBQcm9kdWN0IEd1aWRlClJlYWQgaG9uZXN0ICYgY2FuZGlk IHJldmlld3Mgb24gaHVuZHJlZHMgb2YgSVQgUHJvZHVjdHMgZnJvbSByZWFsIHVzZXJzLgpEaXNj b3ZlciB3aGljaCBwcm9kdWN0cyB0cnVseSBsaXZlIHVwIHRvIHRoZSBoeXBlLiBTdGFydCByZWFk aW5nIG5vdy4KaHR0cDovL2Fkcy5vc2RuLmNvbS8/YWRfaWQ9NjU5NSZhbGxvY19pZD0xNDM5NiZv cD1jbGljawpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpR dWlja2ZpeC11c2VycyBtYWlsaW5nIGxpc3QKUXVpY2tmaXgtdXNlcnNAbGlzdHMuc291cmNlZm9y Z2UubmV0Cmh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL3F1aWNr Zml4LXVzZXJzCgoKKioqCgoKCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKiBBVklTTyBM RUdBTCAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKCkxhIGluZm9ybWFjafNuIGNvbnRl bmlkYSBlbiBlc3RlIG1lbnNhamUgZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIHN1IGRlc3RpbmF0 YXJpby4gTm8gZGViZSBjb3BpYXJzZSwgdHJhbnNtaXRpcnNlIGEgdGVyY2Vyb3MgbmkgZ3VhcmRh cnNlIHBvciBlc3RvcyD6bHRpbW9zLCBzYWx2byBhdXRvcml6YWNp824gZGVsIHJlbWl0ZW50ZS4K ClB1ZWRlIGNvbnRlbmVyIGluZm9ybWFjafNuIGNvbmZpZGVuY2lhbCBvIGxlZ2FsbWVudGUgcHJv dGVnaWRhIGN1eW8gculnaW1lbiBsZWdhbCBkZSB1dGlsaXphY2nzbiBubyBzZSB2ZSBhZmVjdGFk byBwb3IgZWwgaGVjaG8gZGUgcXVlIGhheWEgc2lkbyBlbnZpYWRhIHBvciBjb3JyZW8gZWxlY3Ry 825pY28uCgpTdSBlbnbtbyBwb3IgZXJyb3IgYSB1bmEgcGVyc29uYSBkaXN0aW50YSBkZSBzdSBk ZXN0aW5hdGFyaW8gcmVhbCBubyBpbXBsaWNhIHF1ZSBzZSBoYXlhIG1vZGlmaWNhZG8gdGFsIGRl c3RpbmF0YXJpbyBuaSBzdXBvbmUgcmVudW5jaWEgYSBzdSBldmVudHVhbCBjYXLhY3RlciBjb25m aWRlbmNpYWwgbyBhbCBy6WdpbWVuIGxlZ2FsIHF1ZSByaWphIHN1IHV0aWxpemFjafNuLgoKQ3Vh bHF1aWVyIG9waW5p824gZXhwcmVzYWRhIGVuIGVzdGUgbWVuc2FqZSB2aW5jdWxhcuEgZXhjbHVz aXZhbWVudGUgYSBsYSBwZXJzb25hIHF1ZSBsbyBoYXlhIHJlbWl0aWRvLCBleGNlcHRvIGN1YW5k byBlbCBtZW5zYWplIGVzdGFibGV6Y2EgbG8gY29udHJhcmlvIHkgZWwgcmVtaXRlbnRlIGVzdOkg YXV0b3JpemFkbyBwYXJhIGVzdGFibGVjZXIgcXVlIGRpY2hhcyBvcGluaW9uZXMgdmluY3VsYXLh biBhIGVzdGEgZW50aWRhZC4gCgpFbiBlbCBzdXB1ZXN0byBkZSBxdWUgZXN0ZSBjb3JyZW8gc2Ug cmVjaWJpZXJhIHBvciBlcnJvciwgcm9nYW1vcyBwcm9jZWRhbiBhIGJvcnJhcmxvLCBzaW4gcmVl bnZpYXJsbyBhIHRlcmNlcm9zIG5pIGNvbnNlcnZhcmxvIGVuIGN1YWxxdWllciBzb3BvcnRlIHkg bm9zIGluZm9ybWVuIGlubWVkaWF0YW1lbnRlIGxsYW1hbmRvIGFsIHRlbOlmb25vIDM0IDkxIDU4 OTIxMjMgbyBhIGxhIGRpcmVjY2nzbiBkZSBjb3JyZW8gZWxlY3Ry825pY28gcmVtaXRlbnRlLiBH cmFjaWFzLgoKKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqIERJU0NMQUlNRVIgKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqCgpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRo aXMgbWVzc2FnZSBpcyBmb3IgdGhlIGV4Y2x1c2l2ZSB1c2Ugb2YgdGhlIG5hbWVkIHBlcnNvbi4g SXQgY2FuIG5vdCBiZSBjb3BpZWQsIHRyYW5zbWl0dGVkIHRvIHRoaXJkIHBhcnRpZXMgb3Igc3Rv cmVkIGJ5IHRoZSBsYXR0ZXIsIGV4Y2VwdCBpZiBhdXRob3Jpc2VkIGJ5IHRoZSBzZW5kZXIuCgpJ dCBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgbGVnYWxseSBwcml2aWxlZ2VkIGluZm9ybWF0 aW9uIHdob3NlIGxlZ2FsIHJlZ2ltZSBpcyBub3QgYWZmZWN0ZWQgYnkgdGhlIGZhY3QgdGhhdCB0 aGlzIGluZm9ybWF0aW9uIGhhcyBiZWVuIHNlbnQgYnkgZS1tYWlsLiAKCkl0cyBlcnJvbmVvdXMg dHJhbnNtaXNzaW9uIHRvIGEgcGVyc29uIG90aGVyIHRoYW4gdGhlIHJlYWwgbmFtZWQgcGVyc29u IG5laXRoZXIgaW1wbGllcyBhbnkgbW9kaWZpY2F0aW9uIG9mIHRoaXMgbmFtZWQgcGVyc29uIG5v ciBhIHJlbnVuY2lhdGlvbiBvZiB0aGUgZXZlbnR1YWwgY29uZmlkZW50aWFsaXR5IG9yIGxlZ2Fs IHJlZ2ltZSBhZmZlY3RpbmcgdGhlIHVzZSBvZiBjb25jZXJuZWQgbWVzc2FnZS4KIApBbnkgdmll d3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgYmluZGluZyBleGNsdXNpdmVseSB1cG9u IHRoZSBpbmRpdmlkdWFsIHNlbmRlciwgZXhjZXB0IHdoZXJlIHRoZSBtZXNzYWdlIHN0YXRlcyBv dGhlcndpc2UgYW5kIHRoZSBzZW5kZXIgaXMgYXV0aG9yaXNlZCB0byBiaW5kIHRoaXMgZW50aXR5 LiAKCklmIHlvdSByZWNlaXZlIHRoaXMgbWVzc2FnZSBpbiBlcnJvciwgcGxlYXNlIGRlbGV0ZSBp dCB3aXRob3V0IHRyYW5zbWl0dGluZyBpdCB0byBhbnkgdGhpcmQgcGFydHkgb3Iga2VlcGluZyBp dCBpbiBhbnkgZm9ybSBhbmQgbm90aWZ5IHVzIGltbWVkaWF0ZWx5IGVpdGhlciBieSBwaG9uZSAo MzQgOTEgNTg5MjEyMykgb3IgdXNpbmcgdGhlIGUtIG1haWwgYWRkcmVzcyBvZiB0aGUgc2VuZGVy LiBUaGFuayBZb3UuCg== |
|
From: George M. C. <ge...@qu...> - 2005-04-13 14:02:34
|
I resolved the COM error by entering UseDataDictionary=3DN, now I am=20 trying to get the initiator to succesfully log on to the session. Is it=20 bad not to use the DataDictionary? Thanks for your help! Best, George Guillermo Arbeiza Alameda wrote: >Have you just copied the contents of your config file here? If that's th= e >case you should look carefully to the ConnectionType field: it should be >"initiator" instead of "initator". > >Hope it will help. > >Cheers, >Guillermo. > >-----Mensaje original----- >De: qui...@li... >[mailto:qui...@li...]En nombre de George >M. Coles >Enviado el: martes, 12 de abril de 2005 15:18 >Para: qui...@li... >Asunto: [Quickfix-users] error:no session defined for initiator > > >QuickFIX Documentation: >http://www.quickfixengine.org/quickfix/doc/html/index.html >QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFA= Q >QuickFIX Support: http://www.quickfixengine.org/services.html > >I am trying to use the sample c# application code with a simple config >file. I get the error "no session defined for initiator" in the >constructor of my Intiator object. Here is my code and the config fiel >contents: > >try > { > SessionSettings settings =3D new >SessionSettings(_fileName); > FixApplication application =3D new FixApplication(); > FileStoreFactory storeFactory =3D new >FileStoreFactory(settings); > FileLogFactory logFactory =3D new >FileLogFactory(settings); > MessageFactory messageFactory =3D new >DefaultMessageFactory(); > ThreadedSocketInitiator init =3D new >ThreadedSocketInitiator( application, storeFactory, settings, >messageFactory ); > } > catch(ConfigError e) > { > log.Error( e ); > } > >config file: >[DEFAULT] >ConnectionType=3Dinitator >ReconnectInterval=3D30 >HeartBtInt=3D30 >SenderCompID=3DA > >[SESSION] >BeginString=3DFIX.4.2 >TargetCompID=3DB >SocketConnectPort=3D9890 >SocketConnectHost=3D192.168.1.8 >DataDictionary=3DC:/tools/quickfix/quickfix-bin-vc7-1.9.4/quickfix/spec/= FIX42. >xml > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick >_______________________________________________ >Quickfix-users mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-users > > >*** > > > >****************************** AVISO LEGAL *****************************= * > >La informaci=F3n contenida en este mensaje es para uso exclusivo de su d= estinatario. No debe copiarse, transmitirse a terceros ni guardarse por e= stos =FAltimos, salvo autorizaci=F3n del remitente. > >Puede contener informaci=F3n confidencial o legalmente protegida cuyo r=E9= gimen legal de utilizaci=F3n no se ve afectado por el hecho de que haya s= ido enviada por correo electr=F3nico. > >Su env=EDo por error a una persona distinta de su destinatario real no i= mplica que se haya modificado tal destinatario ni supone renuncia a su ev= entual car=E1cter confidencial o al r=E9gimen legal que rija su utilizaci= =F3n. > >Cualquier opini=F3n expresada en este mensaje vincular=E1 exclusivamente= a la persona que lo haya remitido, excepto cuando el mensaje establezca = lo contrario y el remitente est=E9 autorizado para establecer que dichas = opiniones vincular=E1n a esta entidad.=20 > >En el supuesto de que este correo se recibiera por error, rogamos proced= an a borrarlo, sin reenviarlo a terceros ni conservarlo en cualquier sopo= rte y nos informen inmediatamente llamando al tel=E9fono 34 91 5892123 o = a la direcci=F3n de correo electr=F3nico remitente. Gracias. > >****************************** DISCLAIMER ****************************** > >The information contained in this message is for the exclusive use of th= e named person. It can not be copied, transmitted to third parties or sto= red by the latter, except if authorised by the sender. > >It may contain confidential or legally privileged information whose lega= l regime is not affected by the fact that this information has been sent = by e-mail.=20 > >Its erroneous transmission to a person other than the real named person = neither implies any modification of this named person nor a renunciation = of the eventual confidentiality or legal regime affecting the use of conc= erned message. >=20 >Any views expressed in this message are binding exclusively upon the ind= ividual sender, except where the message states otherwise and the sender = is authorised to bind this entity.=20 > >If you receive this message in error, please delete it without transmitt= ing it to any third party or keeping it in any form and notify us immedia= tely either by phone (34 91 5892123) or using the e- mail address of the = sender. Thank You. > > =20 > |
|
From: Oren M. <or...@qu...> - 2005-04-14 13:52:50
|
That COM problem is fixed in the repository. It has to do with which =20= threading model you are using vs. which one we are trying to use when =20= loading MSXML. Future versions will detect the correct model and load =20= appropriately. In any case it is ok to not use a DataDictionary as long as you do not =20= plan to use repeating groups. Otherwise it is absolutely necessary. =20= If you plan on just doing things like basic order routing with =20 NewOrderSingle, ExecutionReport etc, you will be just fine. --oren On Apr 13, 2005, at 9:02 AM, George M. Coles wrote: > QuickFIX Documentation: =20 > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX FAQ: =20 > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ > QuickFIX Support: http://www.quickfixengine.org/services.html > > I resolved the COM error by entering UseDataDictionary=3DN, now I am =20= > trying to get the initiator to succesfully log on to the session. Is =20= > it bad not to use the DataDictionary? > > Thanks for your help! > > Best, > George > > Guillermo Arbeiza Alameda wrote: > >> Have you just copied the contents of your config file here? If that's = =20 >> the >> case you should look carefully to the ConnectionType field: it should = =20 >> be >> "initiator" instead of "initator". >> >> Hope it will help. >> >> Cheers, >> Guillermo. >> >> -----Mensaje original----- >> De: qui...@li... >> [mailto:qui...@li...]En nombre de = George >> M. Coles >> Enviado el: martes, 12 de abril de 2005 15:18 >> Para: qui...@li... >> Asunto: [Quickfix-users] error:no session defined for initiator >> >> >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX FAQ: =20 >> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> I am trying to use the sample c# application code with a simple = config >> file. I get the error "no session defined for initiator" in the >> constructor of my Intiator object. Here is my code and the config = fiel >> contents: >> >> try >> { >> SessionSettings settings =3D new >> SessionSettings(_fileName); >> FixApplication application =3D new = FixApplication(); >> FileStoreFactory storeFactory =3D new >> FileStoreFactory(settings); >> FileLogFactory logFactory =3D new >> FileLogFactory(settings); >> MessageFactory messageFactory =3D new >> DefaultMessageFactory(); >> ThreadedSocketInitiator init =3D new >> ThreadedSocketInitiator( application, storeFactory, settings, >> messageFactory ); >> } >> catch(ConfigError e) >> { >> log.Error( e ); >> } >> >> config file: >> [DEFAULT] >> ConnectionType=3Dinitator >> ReconnectInterval=3D30 >> HeartBtInt=3D30 >> SenderCompID=3DA >> >> [SESSION] >> BeginString=3DFIX.4.2 >> TargetCompID=3DB >> SocketConnectPort=3D9890 >> SocketConnectHost=3D192.168.1.8 >> DataDictionary=3DC:/tools/quickfix/quickfix-bin-vc7-1.9.4/quickfix/=20= >> spec/FIX42. >> xml >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real =20 >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick >> _______________________________________________ >> Quickfix-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-users >> >> >> *** >> >> >> >> ****************************** AVISO LEGAL =20 >> ****************************** >> >> La informaci=F3n contenida en este mensaje es para uso exclusivo de = su =20 >> destinatario. No debe copiarse, transmitirse a terceros ni guardarse =20= >> por estos =FAltimos, salvo autorizaci=F3n del remitente. >> >> Puede contener informaci=F3n confidencial o legalmente protegida cuyo = =20 >> r=E9gimen legal de utilizaci=F3n no se ve afectado por el hecho de = que =20 >> haya sido enviada por correo electr=F3nico. >> >> Su env=EDo por error a una persona distinta de su destinatario real = no =20 >> implica que se haya modificado tal destinatario ni supone renuncia a =20= >> su eventual car=E1cter confidencial o al r=E9gimen legal que rija su =20= >> utilizaci=F3n. >> >> Cualquier opini=F3n expresada en este mensaje vincular=E1 = exclusivamente =20 >> a la persona que lo haya remitido, excepto cuando el mensaje =20 >> establezca lo contrario y el remitente est=E9 autorizado para =20 >> establecer que dichas opiniones vincular=E1n a esta entidad. >> En el supuesto de que este correo se recibiera por error, rogamos =20 >> procedan a borrarlo, sin reenviarlo a terceros ni conservarlo en =20 >> cualquier soporte y nos informen inmediatamente llamando al tel=E9fono = =20 >> 34 91 5892123 o a la direcci=F3n de correo electr=F3nico remitente. =20= >> Gracias. >> >> ****************************** DISCLAIMER =20 >> ****************************** >> >> The information contained in this message is for the exclusive use of = =20 >> the named person. It can not be copied, transmitted to third parties =20= >> or stored by the latter, except if authorised by the sender. >> >> It may contain confidential or legally privileged information whose =20= >> legal regime is not affected by the fact that this information has =20= >> been sent by e-mail. >> Its erroneous transmission to a person other than the real named =20 >> person neither implies any modification of this named person nor a =20= >> renunciation of the eventual confidentiality or legal regime =20 >> affecting the use of concerned message. >> Any views expressed in this message are binding exclusively upon the =20= >> individual sender, except where the message states otherwise and the =20= >> sender is authorised to bind this entity. >> If you receive this message in error, please delete it without =20 >> transmitting it to any third party or keeping it in any form and =20 >> notify us immediately either by phone (34 91 5892123) or using the e- = =20 >> mail address of the sender. Thank You. >> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real =20 > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dclick > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > |
|
From: Brian E. <azz...@ya...> - 2005-04-29 19:25:14
|
Oren -
What is the purpose of the "what" string in RejectLogon? I had hoped
that this would be used to send a logout message with a Text field
indicating the reason for the logon rejection - in this way, I could
indicate to my clients that there was a bad username or such, but the
"what" field is actually ignored by the Session::next() exception
handler.
I think it might be really useful to be able to generate a logout
message with a Text field when the "what" field of the RejectLogon is
not empty. The following patch would supply this functionality:
Session.cpp
-01181 catch ( RejectLogon& )
+01181 catch ( RejectLogon& e)
01182 {
01183 m_state.onEvent( "Logon rejected" );
+ if (!e.what().empty())
+ generateLogout(e.what());
01184 disconnect();
01185 }
This way, users that did not want to generate logouts could simply
leave out a reason ("what"), while users that wanted to add a logout
just need to set a non-blank reason.
// No logout
throw FIX::RejectLogon();
// Logout with reason
throw FIX::RejectLogon("Bad username or password.");
What do you think? I attempted to work around the problem by calling
generateLogout() prior to throwing the exception, but generateLogout()
is a private method and I don't really want to modify the QuickFIX
code; it makes upgrading a pain.
- Brian Erst
|
|
From: Oren M. <or...@qu...> - 2005-04-30 06:20:40
|
Yeah, this looks like a good idea. I'll look at incorporating it into CVS. --oren On Apr 29, 2005, at 2:25 PM, Brian Erst wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX FAQ: > http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ > QuickFIX Support: http://www.quickfixengine.org/services.html > > Oren - > > What is the purpose of the "what" string in RejectLogon? I had hoped > that this would be used to send a logout message with a Text field > indicating the reason for the logon rejection - in this way, I could > indicate to my clients that there was a bad username or such, but the > "what" field is actually ignored by the Session::next() exception > handler. > > I think it might be really useful to be able to generate a logout > message with a Text field when the "what" field of the RejectLogon is > not empty. The following patch would supply this functionality: > > Session.cpp > > -01181 catch ( RejectLogon& ) > +01181 catch ( RejectLogon& e) > 01182 { > 01183 m_state.onEvent( "Logon rejected" ); > + if (!e.what().empty()) > + generateLogout(e.what()); > 01184 disconnect(); > 01185 } > > This way, users that did not want to generate logouts could simply > leave out a reason ("what"), while users that wanted to add a logout > just need to set a non-blank reason. > > // No logout > throw FIX::RejectLogon(); > > // Logout with reason > throw FIX::RejectLogon("Bad username or password."); > > What do you think? I attempted to work around the problem by calling > generateLogout() prior to throwing the exception, but generateLogout() > is a private method and I don't really want to modify the QuickFIX > code; it makes upgrading a pain. > > - Brian Erst > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 great > events, 4 > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X