Class interface to SCACHE's session managementClass interface is later extension to scached module. API documentation is written from aspect of scache_* -procedural API with comments regarding class interface where necessary. Generally methods and theirs counterpart functions are operationally equal. Differences are on how backend is contacted. Class constructor
Session operations.Functions for session initialization, opening, connecting, renaming and dropping. Sessions are distinguished and opened by client generated session identifier.
Private session storageSession storage is private save space unique to every session. Session storage is persistent over lifespan of session. Generally session storage is for keeping per user private information and collected per user data sensitive to active login.
Shared countersShared counters are path/key addressable atomic 64-bit integers on scached backend common to all sessions assigned on same partition. Shared counters can be generally used for inter session communication, specifically as advisory triggers.
Shared storageShared storage equals to private session storage, but is common and mutually accessible to all sessions residing on same partition. Unlink cache storage described below shared storage never expires stored data until deliberately ordered to. Shared storage can be used for inter session communication with optional aid of shared counters.
Cache operationsCache storage is path/key addressable shared storage common to alle sessions on same partition. Unlike shared storage above, cache expires data exceeding configurable memory limit.
Ring operationsRing storage is double linked circular datatype on scached backend. As like other data operations, rings are addressed by path-prefixed keys. Each key contains one ring, which can be operated with functions below. Rings are shared resource common to all connecting clients assigned to same partition. Values stored to rings are persistent. All data queued to ring must be eventually purged to avoid memory leaking. Rings are mainly for implementing FIFOs, LIFOs and producer-consumers -workqueues.
Misc functionsMiscellaneous utility functions.
Exception classes
|
|