RE: [Quickfix-developers] Session Identification Problem

[Shamanth <sha...@in...>]

Hi Oren
=20
Thanks for the reply, the option of using UserID is very helpful, we =
could do this.:)
=20
But does FIXProtocol allow this? like can we have same sender and =
targetID for two different sessions if the two sessions are different in =
functionality?
or does it say that we need to have a unique combination of senderId and =
targetID.=20
=20
I did go through the FIXProtocol spec, but I could not identify any =
place where it specifically states this.=20
=20
thanks
R Shamanth

-----Original Message-----
From: Oren Miller [mailto:or...@qu...]
Sent: Friday, July 30, 2004 5:19 PM
To: Shamanth
Cc: qui...@li...; =
qui...@li...
Subject: Re: [Quickfix-developers] Session Identification Problem



That's a strange scenario. The way QuickFIX would handle this now is the =
way you don't want to do it, two separate processes. The problem with =
using something like the port to identify the session is twofold. One, =
as Joerg pointed out, it is a transport level concept and not one which =
the fix protocol itself is familiar with. Another problem is that the =
port is not a part of the message. In other words, in a scenario like =
this, you can no longer rely on the contents of the message to identify =
what session it belongs to. This means we would have to rely on some =
meta-data in addition to the FIX message itself to figure out where it =
needs to be routed. I don't have a problem with this necessarily, but I =
don't think and arbitrary attribute like the session port is the way to =
do it.=20


One thing I may consider is something along the lines of a UserID =
configuration field. Something like this:=20


[SESSION]=20

SenderCompID=3DSENDER=20

TargetCompID=3DTARGET=20

UserID=3DMARKETDATA=20


[SESSION]=20

SenderCompID=3DSENDER=20

TargetCompID=3DTARGET=20

UserID=3DORDER=20


This user id would be optional, and it would at least make the id =
meaningful.=20


On Jul 28, 2004, at 7:18 AM, Shamanth wrote:=20


Hi=20


We have a provider who has the two sessions exposed=20

1) For Marketdata=20

2) For Order=20


The problem is both these sessions use same SenderID, SenderSubID, =
TargetID and also the SocketConnectHost the only difference is in the =
port number (SocketConnetPort).=20


How does quickfix can be setup to handle the above situation. We want to =
run only one instance of quickfix servicing both the sessions.=20


thanks=20

R Shamanth=20


  NOTICE=20


This e-mail message and any attachments, which may contain confidential =
information, are to be viewed solely by the intended recipient of =
Integral Development Corp.  If the reader of this message is not the =
intended recipient, you are hereby notified that any use, dissemination, =
distribution or copying of this communication is strictly prohibited.  =
If you have received this message in error, please immediately notify =
the sender and delete the mail and all attachments.