On Tue, Jun 24, 2008 at 5:51 PM, Asanka Abeysinghe <[EMAIL PROTECTED]> wrote:
> Multiple session with different FIX version using same sender-comp-id(Tag > 49) and sender-sub-id(Tag 50) is a very rare case. FIX users make it deffer > to identify the message created place / desk/ trader, so we are on safe > side. And we have an additional field call senderlocation id (Tag 142) for > additional information. Drawback will be to read the tags need to process > the message payload. Exactly. And as long as the FIX applications communicating via Synapse use DeliverTo* and OnBehalf* fields we should be fine. Synapse already is capable of performing the routing based on the values of these fields as specified in the FIX specs. Thanks Best Regards, Hiranya Jayathilaka > Asanka A. > Hiranya Jayathilaka wrote: > >> >> No. When there are multiple FIX sessions of different versions connected >> to the same acceptor, Synapse will have no way of determining how to forward >> the response messages if DeliverToX fields are not in use. So the >> restrictions imposed by the validation prevent the user from doing something >> like that. Anyway as you said, being able to bridge FIX sessions with >> different versions is a great usecase and the above scenario is a very >> special case. So in this case we can afford to remove validation or make it >> an optional feature. >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
