The runtime handle the store is resolved from.
Calls the instance registered under a name.
The runtime handle.
Name identifying the instance.
Path within the instance's own handler.
Optionalinit: RequestInit
Request options — method, headers, body.
The parsed response.
Creates a fresh instance and returns its id.
The runtime handle.
The new instance's id.
Reports whether the capability is actually usable on this runtime.
The runtime handle.
true when calls will reach a real backing resource.
A capability backed by an optional resource answers false when that
resource was never provisioned. Implementations must document what each
method does in that state — degrade or throw — and must not vary it, since
a caller choosing between two implementations is relying on the answer
meaning the same thing in both.
Strongly consistent, single-threaded state addressed by name.
Remarks
The capability for the things a cache cannot do: a counter that must not lose an increment, a lock, a session two requests may touch at once. Every call for a given name reaches the same instance, and that instance handles one request at a time — which is what makes read-modify-write safe here and unsafe in CacheStore.
Addressing is by name rather than by handle so that callers need no discovery step: two callers that agree on a name are talking to the same state.
Author
Bayu Dwiyan Satria
Version
1.0.0
Since
1.0.0