|
By:
gruss does tenths of a second
|
|
By:
Curious....you wrote Fill AND kill.
Did you mean "Fill or kill" ? If not, what is the definition of F "AND" K. |
|
By:
Don't see how any software could do FOK on the Exchange; it's not available as an order type and can't be synthesised.
IOC would be easy enough to do, but IOC allows partial fills. |
|
By:
I know Bet Angel does this. It has fill or kill functions and it can instantly offset or partial offset if using batching. I often use 0.2, 0.5 and so on as the kill delay.
|
|
By:
Shold love to know how that works - I can't see how you can avoid getting partially matched.
|
|
By:
Could someone give an example on Betangel do this? It can't be a complete FOK.
|
|
By:
Since the exchange doesnt offer an explicit FOK order type, you have to "best effort" it by placing the bet, and sending a cancel a short amount of time later. There's no guarantee you wont get partially matched, though.
|
|
By:
@chilly - exactly so. The 'place bet -> cancel as soon as a bet ID comes back' gives IOC neatly enough, but only approaches FOK if you don't mind partial matches - which rather misses the point of FOK :)
|
|
By:
If you were trying to be extremely clever, you might try and guess the betID (if you are a V high frequency trader, this might not be as unrealistic as it sounds). Since you cant cancel bets on another account, you spray in a load of cancels for the guessed betId immediately after you send in the place bet request - cuts down the wait a bit and makes it less likely to get a partial.
|
|
By:
So the "description" of FOK is not correct.
|