Sky Bear Technical Standards - Home
Search
×
FR

Placeholder headline

This is just a placeholder headline

TEMA 2026 Edition – Online Subscription Only

$

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 15SIH, 2nd Edition: Installation and Handling of Spoolable Reinforced Plastic Line Pipe

$

158

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 754, 4th Edition: Process Safety Performance Indicators for the Refining and Petrochemical Industries

$

393

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2020: Power Piping

$

668

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2022: Power Piping

$

668

BUY NOW

ISO 4396:2023

ISO 4396:2023 Telecommunications and information exchange between systems – Recursive inter-network architecture – Part 6: RINA data transfer service

CDN $192.00

SKU: a56b0170290d Category:

Description

This document is a service definition that provides an abstract description of the application programming interface (API) seen by an Application Process using a distributed inter-process communication (IPC) facility (DIF). APIs reflect the specific constraints and conventions of an operating system or programming language. This document does not do that. A service definition specifies the interactions between an Application Process and IPC independent of such specifics.

The application process may be an IPC process and the member of a (N+1)-DIF. Actual APIs will be system specific (or may not exist at all), but this sequence of interaction will be maintained. The notation here is used to emphasize that the participants can only act on what they see and must not make assumptions about any events that may have occurred elsewhere. Hence the primitives are described in terms of primitives invoked locally to cause an action, submit, and primitives locally invoked to deliver information on state.

This is not a design for an API. It cannot be as a basis for any conformance tests. An actual API may make some, all or none of the parameters noted here visible to the user and may add additional primitives of local significance. The purpose of this service definition is to specify information that must or may be available by whatever means, explicit or implicit, to drive the operation of the DIF.

Edition

1

Published Date

2023-12-05

Status

PUBLISHED

Pages

14

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

This document is a service definition that provides an abstract description of the application programming interface (API) seen by an Application Process using a distributed inter-process communication (IPC) facility (DIF). APIs reflect the specific constraints and conventions of an operating system or programming language. This document does not do that. A service definition specifies the interactions between an Application Process and IPC independent of such specifics.

The application process may be an IPC process and the member of a (N+1)-DIF. Actual APIs will be system specific (or may not exist at all), but this sequence of interaction will be maintained. The notation here is used to emphasize that the participants can only act on what they see and must not make assumptions about any events that may have occurred elsewhere. Hence the primitives are described in terms of primitives invoked locally to cause an action, submit, and primitives locally invoked to deliver information on state.

This is not a design for an API. It cannot be as a basis for any conformance tests. An actual API may make some, all or none of the parameters noted here visible to the user and may add additional primitives of local significance. The purpose of this service definition is to specify information that must or may be available by whatever means, explicit or implicit, to drive the operation of the DIF.

Previous Editions

Can’t find what you are looking for?

Please contact us at: