Heartbeat function?

[heja]

The Betdaq API has a very useful function, the so-called Heartbeat. If you register a Heartbeat, you should send Pulse calls in order to notify the server you are still online. If you do not send Pulse within a specified amount of time, all your unmatched bets will be cancelled in order to avoid matching of orders you cannot supervise anymore due to net problems.

Is there a chance to introduce such a feature in the new API?

[AlgoTrader]

The old API 6 has keepAlive method thbat is very similar. It does nothing, just extend current session and prevent HTTPS connections from being closed.

It is also very good for testing network performance. I achived many hundreds of keepAlive calls a second and I did not worried to DDOS Betfair servers.

I fully support the need of keepAlive / heartbeat methods. And we cannot have it on auth server only, I need to keep conections open to regular API also

[heja]

The keepAlive service of the API 6 is very different from the Betdaq Heartbeat. The aim of the keepAlive is to maintain the connection to the server to avoid the need for establishing a new connection for further requests. However, the Heartbeat is to save the player's position in the case of a net breakdown. If you play a strategy that needs continuous monitoring of your bets and canceling them when necessary, this could be a very helpful feature that saves you a lot of money when the network fails on either the user's side or at Betfair.

[AlgoTrader]

Thanks for explaining Betdaq heartbeat. That's real cool stuff