☜	OMI - Protocol Stack Draft MDC Standard					☞

B.4 Protocol stack

The designers of OMI intend it to work well in implementations that include other network services, including proprietary protocols providing the same database functions. Because OMI relies on an externally supplied transport protocol, its success at sharing network hardware and software depends on the generality of the vendor’s network software services.

OMI network managers face a more complex task than those purchasing a proprietary network from 1 vendor who takes responsibility for making everything work. As with any mixed-vendor system, the customer assumes that responsibility or pays a system integrator to do so. For a successful network the vendors must offer – and the customer must choose – a compatible stack of protocols at the transport level and at each lower level down to the hardware connection. (Gateways between unlike protocols are available.) Any method that provides an error-free, sequence-preserving path for messages containing all 8-bit characters is suitable.

NOTE – Therefore, a serial line interface could not use special characters for flow control or other purposes unless a protocol below OMI mediates to permit all 256 characters for OMI messages.

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:50:56.

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