Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bet request client caching #14

Open
varneyo opened this issue Dec 22, 2021 · 0 comments
Open

Bet request client caching #14

varneyo opened this issue Dec 22, 2021 · 0 comments

Comments

@varneyo
Copy link
Collaborator

varneyo commented Dec 22, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant