☜	OMI - Extensions Draft MDC Standard					☞

4.12 Extensions to the standard

OMI admits extensions for specific implementations or for specific applications. Extensions to the standard may afford increased performance in homogeneous networks, add proprietary functions, or enable experimentation with features planned for new versions of OMI.

Implementers shall register their extensions with the MUMPS Development Committee, the sponsor of ANSI/MDC X11.2, to assure uniqueness. 2 numbers identify an extension; an operation class and an error class. Each class comprises 65 536 values.

An extension may coexist with other extensions. The agent and the server shall notify each other of their available extensions when establishing the session, and they may use any number of these extensions during the session.

Implementers define extensions, and they shall bear responsibility for conflicts with the standard and among extensions. An implementation that provides an extension shall also provide the standard protocol.

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 07-Mar-2004, 10:20:10.

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