Imported from previous forum
Does it be possible use HTTP for transport FIX ?. The paradigm request/response is always valid ?
[ original email was from Nikhil Bose - assistsoft@yahoo.com ]
> Does it be possible use HTTP for transport FIX ?. The paradigm request/response is always valid ?
>
Hi,
Even if its theoretically possible to do that, why would you want to do that. The value of FIX is in that you can connect to any FIX engine as long as both of you speak the same FIX protocol. As far as I know, most commercially available FIX engines use TCP/IP. If you chose to use HTTP, you would probably only be able to connect to another instance of your own engine, which would be very limiting.
If you are defining your own protocol, in a sense, you might as well use your own message format, etc. The problem with HTTP is that if you follow the standard HTTP Server and client model, there is no automatic "push" of messages from the server side. You have to have a HTTP server on both ends.
And ofcourse there are lots of very good TCP/IP based FIX engines already available to suit every budget.
Regards,
Nikhil
> > Does it be possible use HTTP for transport FIX ?. The paradigm request/response is always valid ?
> >
>
> Hi,
>
> Even if its theoretically possible to do that, why would you want to do that. The value of FIX is in that you can connect to any FIX engine as long as both of you speak the same FIX protocol. As far as I know, most commercially available FIX engines use TCP/IP. If you chose to use HTTP, you would probably only be able to connect to another instance of your own engine, which would be very limiting.
>
> If you are defining your own protocol, in a sense, you might as well use your own message format, etc. The problem with HTTP is that if you follow the standard HTTP Server and client model, there is no automatic "push" of messages from the server side. You have to have a HTTP server on both ends.
>
> And ofcourse there are lots of very good TCP/IP based FIX engines already available to suit every budget.
>
> Regards,
> Nikhil
>
>
Hi Nikhil
Thank you for your quick answer. I am working in a project for Madrid Stock Exchange (Spain) and their service of multimarket orders over NT.The reason of the use of HTTP is the integration with other OFX services (Open Financial Conectivity) developed already like a WEB server extension and that they use HTTP. We are thinking of using FIX but was sought to use HTTP or MSMQ traffic (Microsoft Queues). OFX (MS Money) uses HTTP unsolicited responses not requested and we thought that FIX could be made the same although it don’t seem very correct.
From the FIX engines, that do you know which do you believe that he more interesting?, with source code in C/C++ and with a relationship quality/price reasonable.
Greetings
Jose Luis
[ original email was from Nikhil Bose - assistsoft@yahoo.com ]
Hi Jose,
Do you have any other e-mail address you can be reached at? All mail to jlmg@iberia-inf.es is bouncing.
Nikhil