☜	OMI - Sessions Draft MDC Standard					☞

4.3.1 Sessions

OMI uses 1 circuit to establish a session between exactly 2 OMI nodes. However, implementers may supply servers that support many sessions, to give several client nodes access to the server node’s database. Implementers may also permit more than 1 session on a client node, so that different client processes may refer to data on several server nodes. However, a particular client shall connect to a particular server through only 1 session at a time, because duplicate paths between a client and a server could cause transactions to be processed out of sequence.

Initiation and termination of sessions shall be invisible to application programs. The implementation shall establish and terminate sessions as necessary to perform OMI operations.

A session is not symmetric. Requests from 1 client node are satisfied at the other server node. Another session is needed to handle requests in the opposite direction.

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:45:44.

For comments, contact Ed de Moel (demoel@jacquardsystems.com)