You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possibility of adding in client caching of bet request as second retrieval of bets requires using the bet_request_id.
Options could be to store for X time period, till the start time has passed, etc. Maximum number of bet_request stored.
bet_request_get - could have an additional parameter (cache_result)
Is this required or leave it up to the user. Once requested if the bet_request_id is not stored then those results wont be able to be access anymore. Either way as soon as the process is stopped there is no way to re-access those bet requests.
The text was updated successfully, but these errors were encountered:
Possibility of adding in client caching of bet request as second retrieval of bets requires using the bet_request_id.
Options could be to store for X time period, till the start time has passed, etc. Maximum number of bet_request stored.
Is this required or leave it up to the user. Once requested if the bet_request_id is not stored then those results wont be able to be access anymore. Either way as soon as the process is stopped there is no way to re-access those bet requests.
The text was updated successfully, but these errors were encountered: