You should keep in mind, that the isolation level by default is per-component,
not per-request. If you, for example, have the same component active twice
(through dynamic_load) you have to manually ensure, that each request is
treated separately. Unfortunately MidCOM cannot help you here.

Implementation Notes:

This is a simple wrapper that provides access to the sessioning singleton.
It has the same public member functions as midcom_services__sessioning, refer
to this class for a detailed documentation.

Basically this wrapper ensures the singleton pattern is maintained and provides
you with an easy way of lock the domain you're working in.

Returns

Tags

set()

Note, that a copy is stored,
the actual object is not referenced in the session data. You will have to update
it manually in case of changes.

Parameters

mixed

$key

Session value identifier.

mixed

$value

Session value.

Tags

None found

exists()

exists(mixed $key) : boolean

Checks, if the specified key has been added to the session store.

This is often used in conjunction with get to verify a keys existence.

Parameters

mixed

$key

The key to query.

Returns

boolean
—

Indicating availability.

Tags

None found

remove()

remove(mixed $key) : mixed

Removes the value associated with the specified key. Returns null if the key
is non-existent or the value of the key just removed otherwise. Note, that
this is not necessarily a valid non-existence check, as the sessioning
system does allow null values. Use the exists function if unsure.