RE: [Quickfix-developers] Another Logon Question

[Jon D. <jd...@Li...>]

Oren,
=20
    So you are saying in the engine I am developing ( executor example =
), the Logon Message will be signaled in the fromAdmin() handler?

-----Original Message-----
From: Oren Miller [mailto:ore...@ya...]
Sent: Thursday, May 22, 2003 4:30 PM
To: Jon Dahl; qui...@li...
Subject: Re: [Quickfix-developers] Another Logon Question


Jon,
=20
You can do this in either the toAdmin method or the onMessage(), if you =
are using a MessageCracker in toAdmin.  When someone sends you a logon, =
this will go to your toAdmin call.  You will notice that one of the =
throw specifiers on onAdmin is RejectLogon.  So when you get a logon =
message, you need to validate the password they send with the one =
associated with their sessionid (or just the TargetCompID, depending on =
how you do it).  If the passwords don't match, throw a RejectLogon and =
they will be disconnected.
=20
onLogon will only get called after a succesful logon, so you don't have =
to worry about false poisitives there.  You can do whatever logon =
processing is required. =20
=20
The onCreate method only gets called once for each session.  This just =
lets you know that the session class has been created and you can begin =
sending messages to it (you don't need to wait for someone to logon =
before sending them stuff).  If they arn't logged on, they will get it =
during a resend request whenever they do logon.
=20
Jon Dahl <jd...@Li...> wrote:

Hello All,

I have somewhat of a long winded set of questions here, so bear with me =
please.

I have been working with the quickfix library for a few weeks now and =
have to say I love it.
The folks at thoughtworks have done a great job.

I have most of the functionality I need in a service but one thing - =
Logon's. It escapes me where I need
to authenticate a user against a db, flat file, etc. I have searched the =
mail lists for logons
(sourceforge really needs to improve their searches -- can you say =
google) and haven't really found anything
definitive.

So let's say I have a service started that is waiting for connection X =
to connect, what actually happens when
the client X connects to the service?

Where should the logon be handled and verified against a security =
identifier?
1. OnCreate
2. OnLogon
3. onMessage( FIX43::Logon&, FIX::SessionID&)
4. toAmdin

Thanks,

JD



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers



  _____ =20

Do you Yahoo!?
The New  =
<http://us.rd.yahoo.com/search/mailsig/*http://search.yahoo.com> Yahoo! =
Search - Faster. Easier. Bingo.