Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
<p>This Recommendation | International Standard is based on the framework of abstractions and concepts developed in the</p>
<p>Reference Model for Open Distributed Processing (ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 |</p>
<p>ISO/IEC 10746-3).</p>
<p>This Recommendation | International Standard defines how interactions between computational objects in a</p>
<p>computational specification of a system relate to protocol support for those interactions in an engineering specification of</p>
<p>that system. In particular it:</p>
<p>? defines a General Interworking Framework (GIF);</p>
<p>? within the GIF, defines a set of facilities each comprising a set of functionally-related service primitives as</p>
<p>abstract definitions of the interactions of basic engineering objects and channel objects;</p>
<p>? defines the parameters of the service primitives of the GIF;</p>
<p>? defines the permitted sequence of the service primitives by means of state tables;</p>
<p>? specifies, in annexes, the mapping of the GIF service primitives and their parameters to the messages and</p>
<p>fields of particular protocols.</p>
<p>As specified in this Recommendation | International Standard, the GIF defines protocol support for a pragmatic subset of</p>
<p>the possible computational interactions defined in ITU-T Rec. X.903 | ISO/IEC 10746-3. It is also restricted in the</p>
<p>features of the protocol support and the supported transparencies.</p>
<p>The GIF, as specified here, defines:</p>
<p>? support for computational operations, but not for streams;</p>
<p>? support using stub, binder and protocol objects hierarchically, such that any interaction at the interworking</p>
<p>reference point of the supporting protocol object supports liaisons of one of those objects or of the basic</p>
<p>engineering object, and any interaction to support those liaisons is passed via that interworking reference</p>
<p>point; and</p>
<p>? interactions at a single interworking reference point, from the perspective of one side; interceptors are not</p>
<p>explicitly considered;</p>
<p>NOTE 1 ? It is intended that the GIF could be extended, in a future amendment, to support streams and flows. The present</p>
<p>specification is restricted to areas that are technically stable.</p>
<p>The GIF supports at least some forms of:</p>
<p>? access transparency; and</p>
<p>? location transparency.</p>
<p>The GIF as specified here also supports a limited equivalent of relocation transparency. Other transparencies are not</p>
<p>addressed in this present specification.</p>
<p>NOTE 2 ? It is intended that the GIF could be extended, in future amendments, to support additional transparencies.</p>
<p>The GIF does not explicitly model Quality of Service requirements.</p>
<p>The application of security-related issues to the GIF are not included in the current text and are for further study.</p>
<p>The set of mappings to particular protocols specified in annexes to this Recommendation | International Standard is not</p>
<p>exhaustive. The GIF could be mapped to other protocols.</p>
<p>NOTE 3 ? In particular, a mapping to the DCOM protocol family would be a candidate for an additional annex.</p>
Reģistrācijas numurs (WIID)
25488
Darbības sfēra
<p>This Recommendation | International Standard is based on the framework of abstractions and concepts developed in the</p>
<p>Reference Model for Open Distributed Processing (ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 |</p>
<p>ISO/IEC 10746-3).</p>
<p>This Recommendation | International Standard defines how interactions between computational objects in a</p>
<p>computational specification of a system relate to protocol support for those interactions in an engineering specification of</p>
<p>that system. In particular it:</p>
<p>? defines a General Interworking Framework (GIF);</p>
<p>? within the GIF, defines a set of facilities each comprising a set of functionally-related service primitives as</p>
<p>abstract definitions of the interactions of basic engineering objects and channel objects;</p>
<p>? defines the parameters of the service primitives of the GIF;</p>
<p>? defines the permitted sequence of the service primitives by means of state tables;</p>
<p>? specifies, in annexes, the mapping of the GIF service primitives and their parameters to the messages and</p>
<p>fields of particular protocols.</p>
<p>As specified in this Recommendation | International Standard, the GIF defines protocol support for a pragmatic subset of</p>
<p>the possible computational interactions defined in ITU-T Rec. X.903 | ISO/IEC 10746-3. It is also restricted in the</p>
<p>features of the protocol support and the supported transparencies.</p>
<p>The GIF, as specified here, defines:</p>
<p>? support for computational operations, but not for streams;</p>
<p>? support using stub, binder and protocol objects hierarchically, such that any interaction at the interworking</p>
<p>reference point of the supporting protocol object supports liaisons of one of those objects or of the basic</p>
<p>engineering object, and any interaction to support those liaisons is passed via that interworking reference</p>
<p>point; and</p>
<p>? interactions at a single interworking reference point, from the perspective of one side; interceptors are not</p>
<p>explicitly considered;</p>
<p>NOTE 1 ? It is intended that the GIF could be extended, in a future amendment, to support streams and flows. The present</p>
<p>specification is restricted to areas that are technically stable.</p>
<p>The GIF supports at least some forms of:</p>
<p>? access transparency; and</p>
<p>? location transparency.</p>
<p>The GIF as specified here also supports a limited equivalent of relocation transparency. Other transparencies are not</p>
<p>addressed in this present specification.</p>
<p>NOTE 2 ? It is intended that the GIF could be extended, in future amendments, to support additional transparencies.</p>
<p>The GIF does not explicitly model Quality of Service requirements.</p>
<p>The application of security-related issues to the GIF are not included in the current text and are for further study.</p>
<p>The set of mappings to particular protocols specified in annexes to this Recommendation | International Standard is not</p>
<p>exhaustive. The GIF could be mapped to other protocols.</p>
<p>NOTE 3 ? In particular, a mapping to the DCOM protocol family would be a candidate for an additional annex.</p>
