Skip to content

interfaces provide no way to plumb context through to store #57

@jhump

Description

@jhump

Stores that need to utilize the network (so any store that isn't purely in-memory) really want a context.Context. The current APIs, both RateLimiter and GCRAStore, have no affordance for contexts. This means that things like deadline propagation and cancellation cannot be made to work, to curtail work in the event that communications with the store are slow.

This also problematic for some runtime environments, such as the Google App Engine standard runtime for Go. Access to all App Engine services that might implement the store (memcache, dataastore, etc) all require a context.Context, and the background context does not suffice since the context must be scoped to a particular incoming HTTP request.

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