|
|
|
Description |
Transactional, type-indexed implementation of server-side state.
Glossary
A transactional entity (TE) is a named multi-versioned global variable.
|
|
Synopsis |
|
|
|
Documentation |
|
|
Handle of a transactional variable
|
|
|
|
Attempt to create a new tv n and set its initial value. Returns handle to
the variable. If the variable already exists, then just returns the handle.
|
|
|
Create a fresh transactional variable with an initial value and return its
handle. Performs a physical write to ensure that the variable's name is
unique. Locks the transaction directory during the write operation.
|
|
|
Remove a transactional variable. Subsequent read accesses to this variable
will make the transaction fail. May throw an exception if the variable is not
present.
|
|
|
Read transactional variable through a typed handle.
|
|
|
Write to a transactional variable through typed handle. Only affects the
log, no physical write happens. Checks physically for existence of the
variable (but tries the log first). Raises exception if it does not exist.
|
|
|
|
data Control cgi result | Source |
|
Constructors | Control | | abandon :: result -> cgi () | abandon with result (rollback)
| setFail :: result -> cgi () | set result on failure
| setCommit :: result -> cgi () | set result on successful commit
|
|
|
|
|
|
Type of a CGI action in a transactional scope with a result variable of
type a.
|
|
|
Produced by Haddock version 2.6.0 |