☜	OMI - Multiple Requests per Message Draft MDC Standard					☞

B.9 Multiple requests per message

The provision of many requests and many responses per message spreads the overhead of message transmission across many transactions, especially when the agent can combine requests from many client programs. Even for a single M[UMPS] client, many set and kill transactions may profitably be combined, although the M[UMPS] client must usually await the response to other types of operations before proceeding. Non-M[UMPS] clients, and perhaps highly optimized M[UMPS] clients, could, however, usefully combine other operations, for example, to request many items from the database at once.

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, 13:34:18.

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