Better to Update Bet or Cancel and Re-Place

[monkeymagix]

Hi

After reading the API documentation it seems all a ReplaceInstruction call does is cancel the bet and replace it at a new price / amount.

Therefore is there any benefit to using the update bet method to update a bets price as opposed to cancelling it myself and then re-placing it?

What do other people do?

Thanks

Rob

[jabe]

Hi

After reading the API documentation it seems all a ReplaceInstruction call does is cancel the bet and replace it at a new price / amount.

Therefore is there any benefit to using the update bet method to update a bets price as opposed to cancelling it myself and then re-placing it?

What do other people do?

Thanks

Rob

Don't know; wondering if it might allow you to avoid the in-play bet delay. Perhaps I'll know in the near future.

[AlgoTrader]

Hi

After reading the API documentation it seems all a ReplaceInstruction call does is cancel the bet and replace it at a new price / amount.

Therefore is there any benefit to using the update bet method to update a bets price as opposed to cancelling it myself and then re-placing it?
Rob

Replacing bet changes price only, it cannot change its size. Changing price always cause losing the bet queue position, the bet is placed into the new price queue tail (if no offers to match immediately).

There is no much difference from cancelling and placing a new bet in parallel. There is small risk that one operation can fail, but I consider it quite negligible.

to change the bet size we can either cancel a portion of a bet or submit an additional bet with the same price

[monkeymagix]

Thanks

Thanks for the responses.

Seems there is little point then changing my code as I am changing the price and or amount and I am handling any issues with cancellation at the moment e.g bet_taken_or_lapsed, errors, connection issues and so on.

Therefore I might as well carry on with my own cancel, if successful, re-place, if partial cancel, set a new partial bet accomodating the existing portion taken etc.

Thanks