Simmer Down Mr. hftvol:
No one here is really interested in this style of theatrics.
If you choose to listen you may learn something too from this generally positive discussion. No one is stopping you or criticizing your programming/data conversion choices.
Makis knows this subject matter from the inside and very well.
The API layer is clearly client side.
Read the B-Pipes docs your posting and you should have realized your converting string representations of prices.
Page 119 Schemas
Event Type: The requested data event type
TRADE string Corresponds to LAST_PRICE
BID_BEST string Depending on the exchange bid ticks will be
returned as BID, BID_BEST or BEST_BID.
ASK_BEST string Depending on the exchange ask ticks will be
returned as ASK, ASK_BEST or BEST_ASK.
Example Syntax: request.Set("eventType", "TRADE");
*** Edit ***
I'm correcting myself here: just read page 151
prices are Float64
**********
Obviously you've got some coding skills... Calculate adding the expense of string conversions to your data types and see how much hardware you'll need to process 10 Million messages a second.
Maybe Bloomberg carries a respected brand name but B-PIPE API is not cream of the crop. I think you were on the right track with Nanex NxCore.
Just keep this discussion civil and productive. If you want to call bull shit do it through PM's.
No one here is really interested in this style of theatrics.
If you choose to listen you may learn something too from this generally positive discussion. No one is stopping you or criticizing your programming/data conversion choices.
Makis knows this subject matter from the inside and very well.
The API layer is clearly client side.
Read the B-Pipes docs your posting and you should have realized your converting string representations of prices.
Page 119 Schemas
Event Type: The requested data event type
TRADE string Corresponds to LAST_PRICE
BID_BEST string Depending on the exchange bid ticks will be
returned as BID, BID_BEST or BEST_BID.
ASK_BEST string Depending on the exchange ask ticks will be
returned as ASK, ASK_BEST or BEST_ASK.
Example Syntax: request.Set("eventType", "TRADE");
*** Edit ***
I'm correcting myself here: just read page 151
prices are Float64
**********
Obviously you've got some coding skills... Calculate adding the expense of string conversions to your data types and see how much hardware you'll need to process 10 Million messages a second.
Maybe Bloomberg carries a respected brand name but B-PIPE API is not cream of the crop. I think you were on the right track with Nanex NxCore.
Just keep this discussion civil and productive. If you want to call bull shit do it through PM's.
Quote from hftvol:
You are a total cheat!!! Not only do you talk bullshit on the C thread but here as well.
Here is the Bloomberg B-PIPE API, anyone can see on page 119 and following that you are simply wrong. You are an evil minded troll who makes up lies or you really have no clue, but for a matter of fact you make up stories:
http://www.openbloomberg.com/files/2012/03/blpapi-developers-guide.pdf
Even though ITCH(nasdaq feed) pumps out prices with decimals (NO CONVERSION), just that they show the full integer as one integer and the fractional part as another integer, THERE IS NO CONVERSION TO INTEGERS GOING ON IN THIS FEED AT ALL, HENCE NO CONVERSION FACTOR.
Reference: your own API documentation link
Next: BATS, they disseminate prices as byte arrays. ALSO FULL DECIMAL representation when converted to actually value type. AGAIN YOU ARE WRONG, NO INTEGER CONVERSION GOING ON
Reference: Your own link.
Next: OPRA: Same here, byte arrays, prices are, after conversion of pure decimal type. NO INTEGER CONVERSION GOING ON HERE AS WELL!!!
Reference: your own link.
You know nothing at all about data feeds and this post makes it abundantly clear!!!
ET is full of morons like you and I call you a cheat and liar because you lied!!! If I get booted off this site for saying that then so be it, I do not have a problem with that. But fact remains that you claim to know things which just flow into your face and which are just plain wrong!!!
, had to come back...