Perl API for FIX Protocol
- Thread starter ndawood
- Start date
It really is a lot more consistent than you seem to think.
Prove it to yourself. Traceroute your broker (or whatever) every day and look at the results. The exact routers may not be the same, but if you look carefully at the names, you'll see that they'll mostly be in the same locations.
For example, my trace to IB looks like:
local provider
LAX Level3
ALTERNET-Level3 bridge
LAX ALTERNET
NYC ALTERNET
IB-ALTERNET gateway
The only time this changes is if there's a major net problem somewhere along the way (very rare).
I'd be a happy camper if lived in the NYC area. Or if I had a broker that was on Level3 in LA, to which I get ping times in the 12-17ms range.
linuxtrader
Guest
What we have done ..... Each subsystem outputs XML ... So the FIX system accepts a document, parses it and can request storage in a compliant form: if a data request then it provides compliant XML.
.. as for the PERl API testing we had a number of issues that make it unsuitable for our use ....too many to go into detail since the failures from our testing listed more than 60 points. This is just for us however.... for many users the solution could probably be made workable.
http://www.futuresindustry.org/fimagazi-1929.asp?a=982
Interesting article by the technical chair of the Fix standards group on the outlook for the protocol in 05'
Good luck and good trading
Bsulli
Interesting article by the technical chair of the Fix standards group on the outlook for the protocol in 05'
Good luck and good trading
Bsulli
This is an update on something I posted in this thread going back to last Nov. Originally posted on implicit tagging in the fix protocol being developed. Well a proof in concept test of the protocol has now been done. New version of Fix is called Fast Protocol.
Bsulli
From Wallstreet & Technology
FIX Organization Tests Fast Protocol
FIX Protocol Ltd. (FPL) released initial results from a proof of concept (POC) developed by FPL's Market Data Optimization Working Group in response to the growth of electronic trading volumes and market data message rates.
The POC consisted of a series of tests applied to a new data compaction methodology called FIX Adapted for Streaming, also known as the Fast Protocol.
The results indicate that the proposed encoding algorithm is fast enough to keep up with data rates of more than 10 Mbit/second and in some cases more than 50 Mbit/second, according to the release. Testing demonstrated 79 percent to 89 percent peak utilization rates when compared to the original size of the data source. CPU utilization was measured at 3.4 microseconds per message (or 294,000 messages per second) or less. The sample data sets in the initial phase of the POC are Archipelago, Exchange's ArcaBook Feed, Options Price Reporting Authority (OPRA) Feed, Chicago Mercantile Exchange (CME) Globex Feed, and Nordic Exchange (NOREX) Feed.
The Fast protocol utilizes implicit tagging, field encoding and serialization in order to radically reduce message size and bandwidth utilization, said the release. According to FPL, with the increased use of direct feeds, coupled with sheer growth in electronic trading volumes and the resultant market data message rates, several market centers and market participants have expressed interest and participated in the FPL Market Data Optimization Working Group activities.
The next phase of the POC will result in the final publication of a reference implementation of the Fast Protocol, a user reference guide and supporting white papers covering best practices. FPL will demonstrate the Fast Protocol at its November 1-2 FPL Electronic Trading Conference in New York.
Bsulli
From Wallstreet & Technology
FIX Organization Tests Fast Protocol
FIX Protocol Ltd. (FPL) released initial results from a proof of concept (POC) developed by FPL's Market Data Optimization Working Group in response to the growth of electronic trading volumes and market data message rates.
The POC consisted of a series of tests applied to a new data compaction methodology called FIX Adapted for Streaming, also known as the Fast Protocol.
The results indicate that the proposed encoding algorithm is fast enough to keep up with data rates of more than 10 Mbit/second and in some cases more than 50 Mbit/second, according to the release. Testing demonstrated 79 percent to 89 percent peak utilization rates when compared to the original size of the data source. CPU utilization was measured at 3.4 microseconds per message (or 294,000 messages per second) or less. The sample data sets in the initial phase of the POC are Archipelago, Exchange's ArcaBook Feed, Options Price Reporting Authority (OPRA) Feed, Chicago Mercantile Exchange (CME) Globex Feed, and Nordic Exchange (NOREX) Feed.
The Fast protocol utilizes implicit tagging, field encoding and serialization in order to radically reduce message size and bandwidth utilization, said the release. According to FPL, with the increased use of direct feeds, coupled with sheer growth in electronic trading volumes and the resultant market data message rates, several market centers and market participants have expressed interest and participated in the FPL Market Data Optimization Working Group activities.
The next phase of the POC will result in the final publication of a reference implementation of the Fast Protocol, a user reference guide and supporting white papers covering best practices. FPL will demonstrate the Fast Protocol at its November 1-2 FPL Electronic Trading Conference in New York.
Yea, well...it's not a big deal to compress the data and stream it down the wire at higher rates of speed. The primary issue and the problems that arise as a consequence of using FIX and XML encoding is that native binary data must be convereted into ASCII and then when it's received the ASCII has to be converted back into binary before any processing can be done!
FIX is flexible, I'll give it that but when it comes to transactional performance (TPS) it'll never be competitive with packetized binary record protocols.
Imagine what the world would be like if the ARP, UDP and TCP protocols were ASCII-TAG encoded...holy cow!
-JMHO
Hi All,
Who uses a linux based FIX solution. How do you connect? Does anybody know about a connector offering also quotes and not requiring XP?
TT promised something like this but seems to drag its feet.
IB talks about its FIX (CTCI) connector and a software manual is available. However, AFAIK information about connections seems non-existant.
Any guidance welcome. Thanks.
nononsense
Who uses a linux based FIX solution. How do you connect? Does anybody know about a connector offering also quotes and not requiring XP?
TT promised something like this but seems to drag its feet.
IB talks about its FIX (CTCI) connector and a software manual is available. However, AFAIK information about connections seems non-existant.
Any guidance welcome. Thanks.
nononsense