Previous | Table of Contents | Next |
Service context IDs are associated with a specific version of GIOP, but will always be allocated in the OMG service context
range. This allows any ORB to recognize when it is receiving a standard service context, even if it has been defined in a
version of GIOP that it does not support.
The following are the rules for processing a received service context:
• The service context is not in the OMG-defined range:
• The service context is in the OMG defined range:
• If it is valid for the supported GIOP version, then it must be processed correctly according to the rules associated with it for that GIOP version level. • If it is not valid for the GIOP version, then it may be ignored by the receiving ORB, however it must be passed on through a bridge and must be made available to interceptors. No exception shall be raised.
• The receiving ORB may choose to ignore it, or process it if it “understands? it, however the service context must be passed
on through a bridge and must made available to interceptors.