Re: [Quickfix-developers] Acceptor expected behavior when on a second connection?

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

> In the case when there already exists a session for a sessionID, what is 
> the expected behavior when the acceptor sees:
>
> - the first session is /not/ logged in, and a second connection is opened 
> for a session where the first message /is/ a login

Until a logon is received, a connection has no way of being associated with 
a session.  So if no logon has been received from a connection, then that 
session is open and up for grabs.

> - the first session is /not/ logged in, and a second connection is opened 
> for a session where the first message is /not/ a login

The first message always needs to be a login.  The connection will simply be 
dropped if it isn't.

> - the first session /is/ logged in, and a second connection is opened for 
> a session where the first message /is/ a login

The second connection will be dropped.  Only one connection is allowed an 
association with the session.  Whoever is there first retains access to that 
session.

> - the first session /is/ logged in, and a second connection is opened for 
> a session where the first message is /not/ a login

Again, the second connection will be dropped because the first message must 
be a login.

--oren