Skip to content

Bet request client caching #14

@varneyo

Description

@varneyo

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions