Re: [Quickfix-developers] Session Identification Problem

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

This is along the lines of what I was thinking.  I've made these=20
changes and checked them into CVS.

--oren

On Aug 2, 2004, at 12:08 PM, Pasquale d'Aloise wrote:

> Hi
> =A0
> I experienced same problem as Shamanth because there are some FIX=20
> market server that implement different services on difference TCP=20
> ports, using same session identifier.
> =A0
> I need to manage more than one simultaneous session with same=20
> SenderID, SenderSubID and TargetID.
> =A0
> I modified my quickfix code inserting a new configuration field=20
> "SessionQualifier". I added a new member "std::string m_strQualifier"=20=

> to class SessionID and I modified all methods to manage that new=20
> member.
> =A0
> I use the class MySQLStore to store sessions info, so I added a new=20
> field "session_qualifier" to my "sessions" table and I manage that=20
> field in my MySQLStore code version.
> =A0
> My code routes well messages to the right destination and I have been=20=

> using this implementation for many months.
> =A0
> Regards.
> Pasquale d'Aloise