|
|
|
|
|
|
|
| ☜ | OMI - TransactionsDraft MDC Standard | ☞ | ||||
An agent shall originate each transaction with exactly 1 request. The server shall attempt the requested operation and shall reply with exactly 1 response, which may indicate failure to perform the operation.
When a request message contains more than 1 request, the requests shall appear in the order of their sequence numbers (see 5.3.1). The server shall process the requests in that order and shall reply with a response message containing the responses, 1 for each request, in that order.
Only the agent shall initiate a transaction. If the server has something to tell the agent, for example "shutting down," the server shall indicate in its next response message that the agent should request the server’s status.
Transactions are isolated. The server need not retain information about completed transactions.
Nonetheless, both server and agent shall retain the parameters of the session including, for example, agent’s and server’s names, and negotiated maximum lengths of gvns, values, and messages.
All OMI transactions shall have the same priority or the same class. That is, there are no out-of-band messages. Protocol management transactions such as capability negotiation, status updates, or startup and shutdown shall be handled in the same manner as database transactions.
|
|
|
|
|
|
|
Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.
Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.
This page most recently updated on 14-Nov-2023, 21:46:04.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)