Hi,

On Tue, Jun 24, 2008 at 4:59 PM, Asanka Abeysinghe <[EMAIL PROTECTED]> wrote:

> Hi Hiranya,
> Jira  issue  is  created.
> Quickfix got a reasonable FIX session + message level validation that even
> use in production systems. Level of the validations will be based on the
> accuracy of the specification used by the user. If more validations required
> user can plug ruby/python scripts to the QF engine.
> Is Synapse using the BeginString to identify the correct endpoint to send
> the responses  back  (I don't think so ) ?


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.

Thanks

Best Regards,
Hiranya Jayathilaka

>
> FIX 4.1 to 4.2 specifications got  lot of  incompatibility  issues  other
> than  that most  of the  versions  are compatible  so  this feature  will be
> useful for  a  FIX  user.
> Cheers
> Asanka A.
>
> Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> Thanks Asankha for the input.
>>
>> We included this validation feature in the FIXTransportSender
>> intentionally because we were not very happy with the level of validation
>> offered by Quickfix/J. Also these restrictions imposed by the transport can
>> help in sending response messages when a service is having multiple sessions
>> on the acceptor side.
>>
>> Anyway what you say also makes perfect sense. Therefore we can consider
>> removing the validation feature from the FIXTransportSender or may be we can
>> consider having that as an optional feature. I have already done this in my
>> local working copy of Synapse. Therefore please raise a JIRA regarding this
>> improvement. Then we can start working on it.
>>
>> Thanks again for your feedback and keep them coming. We need contributions
>> from our users and developers to make the FIX transport a more productive
>> and useful piece of software.
>>
>> Thanks
>>
>> Best Regards,
>> Hiranya Jayathilaka
>>
>> We need feedback from our users and developers to make the FIX transport a
>> more productive and useful piece of software.
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to