network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year |
| seen | May 9 at 5:57 | |
| stats | profile views | 13 |
|
Apr 22 |
comment |
how do you evaluate an FX market aggregator? @Frankie I was adding to your answer in which you mentioned Hotspot and there FIX and java API, as ITCH offers lower latency its an advantage for you market data book. |
|
Apr 22 |
comment |
how do you evaluate an FX market aggregator? Hotspot FX also offers Hotspot ITCH for market data feed. "The advantage of this feed is that clients market data will be as accurate as possible and will not have the possible 50ms delay of the snapshot feed." (Source Knight Hotspot FX website). |
|
Aug 17 |
comment |
FIX Heartbeat message not sent i talked to the counter party again and they said that before they disconnected they sent a test request and got no response from my end so they disconnected. I talked with the QuickFIX/n development team and they suggested i should move onto the latest QuickFIX/n build v1.2.0 and said that this one might be issue #57, which is fixed in v1.2.0. |
|
Aug 16 |
comment |
FIX Heartbeat message not sent Yes, my FIX logs indicate that i sent a heartbeat and the counter-party also confirms all the heartbeat messages that my FIX log file indicates. |
|
May 10 |
comment |
Cross Bid and Ask prices for Forex trading Actually i am working on "Hotspot ECN ITCH Protocol v1.57" |
|
May 4 |
comment |
Resequencing of MsgSeqNum in FIX 4.2 Also i tried Sesssion.setNextTargetMsgSeqNum() but "setNextTargetMsgSeqNum()" or anything similar to it is not available. I am using QuickFIX/n |
|
May 4 |
comment |
Resequencing of MsgSeqNum in FIX 4.2 Yes you are right about Brokers switching the sequence number back. But the above steps are required by the Broker to complete there certification. |
|
May 3 |
comment |
Resequencing of MsgSeqNum in FIX 4.2 Below is the error message i get while QuickFix logs out my application: 20120503-07:19:08.551 : ^8=FIX.4.2^9=115^35=5^34=11^49=***^50=******^52=20120503-07:19:08.550^56=*********^58=MsgSeqNum too low, expecting 9 but received 1^10=211 |
