|
|
|
|
|
|
|
| ☜ | OMI - SessionsDraft MDC Standard | ☞ | ||||
The duration of a session is up to the implementer, considering the relative costs of establishing and maintaining the circuit that supports it. The OMI designers expect a session to last much longer than 1 transaction. It might last as long as both nodes are available, but it also might last for a single transaction only.
The agent process is part of the conception – and perhaps the implementation – of this standard (see 4.3.2). Most transport-level network products offer a limited number of virtual circuits, and some popular server implementations use rather expensive sessions, for example a sub-process per session. The agent allows many clients on a node to share a session with a server. The agent, as the caller of the underlying transport level, can maintain the session while clients come and go.
By allowing the multiplexing of requests, OMI gains more efficient use of network resources at the cost of identifying the user in each transaction.
|
|
|
|
|
|
|
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 13-Sep-2014, 14:30:47.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)