RE: [Quickfix-developers] Session qualifier?

[Steve B. <st...@te...>]

> Oren wrote:
> I suppose because that would cause the messages sent with a TargetSubID, a
> field which may not be supported by the counterparty (this was my
> understanding of the situation).
> 
> I guess I'm not the most knowledgable person regarding this scenario as
> I've never encountered the need for it myself.  I'm open to other
> solutions, but we need to keep in mind that it seems it is pretty 
> commonly used functionality.  I'm ok breaking backwards compatibility 
> if there is a more elegant solution that fits better within the 
> protocol.

It seems to be possible to add the support for optional subIDs and
locationIDs without removing the existing qualifier support. For 
third-party routing, a message would be rejected if the destination 
session is ambiguous due to duplicate TargetComp/Sub/LocationIDs,
even if the qualifiers are different.

Steve

> Again if anyone has comments on this, particularly people who are using
> this functionality, speak up as this will affect you in the future.
> 
> --oren

> -----Original Message-----
> From: Oren Miller [mailto:or...@qu...]
> Sent: Tuesday, July 05, 2005 10:58 AM
> To: Steve Bate
> Subject: Re: [Quickfix-developers] Session qualifier?
> 
> I suppose because that would cause the messages sent with a TargetSubID, a
> field which may not be supported by the counterparty (this was my
> understanding of the situation).
> 
> I guess I'm not the most knowledgable person regarding this scenario as
> I've
> never encountered the need for it myself.  I'm open to other solutions,
> but
> we need to keep in mind that it seems it is pretty commonly used
> functionality.  I'm ok breaking backwards compatibility if there is a more
> elegant solution that fits better within the protocol.
> 
> Again if anyone has comments on this, particularly people who are using
> this
> functionality, speak up as this will affect you in the future.
> 
> --oren
> 
> > Why couldn't that scenario have been handled with the following type of
> > config?
> >
> > [SESSION]
> > SenderCompID=SENDER
> > TargetCompID=TARGET
> > TargetSubID=MARKETDATA
> >
> >
> > [SESSION]
> > SenderCompID=SENDER
> > TargetCompID=TARGET
> > TargetSubID=ORDER
> >
> > Where TargetSubID is used instead of UserID (as in the original
> > message) or session qualifier?
> >
> > Steve
> >
> >