|
|
|
|
|
|
|
| ☜ | OMI - Role of AgentDraft MDC Standard | ☞ | ||||
OMI allows, but does not require, an agent process that multiplexes requests from any number of clients on 1 node in a single session. Thus several clients may share 1 connection to a server, and all OMI servers shall accept multiplexed requests.
NOTE – Although agents are an important conceptual part of this standard, their existence does not affect the form, content, or sequence of messages. A simple implementation could provide 1 client per session, and you may read "client" wherever "agent" appears.
This document describes the agent as a separate process, but an implementation may provide its functions by any method.
The agent is synchronous. A session supports only 1 request message at a time. (The message may contain several requests.) The agent shall send 1 request message and then no more until the server’s response message arrives or the circuit fails.
|
|
|
|
|
|
|
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:54.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)