KB Template
| Summary | Use of POA_Coloc interceptor |
|---|---|
| Environment |
Orbix 6.3.x All supported platforms |
| Question/Problem Description | When should the Orbix POA_Coloc interceptor be used? |
| Clarifying Information |
The POA-Colocation Interceptor (POA_Coloc) optimises communication between clients and servers occupying the same address-space. Specifically, the POA_Coloc distinguishes different objects in the same address space based on their object keys, type IDs and POA names. It then allows these applications to avoid unnecessary marshalling and transmitting procedures when sending requests and replies. This can greatly reduce communication related, performance overheads for collocated applications. |
| Cause | References to collocated and remote direct persistent, server objects, sharing the same object key, type ID and POA name can differ only in host name and port number. As this information is not available to the POA_Coloc interceptor, it is not possible for it to distinguish between collocated and remote objects in this situation. |
| Resolution | The POA_Coloc should be removed from the client binding list when using a mix of collocated and remote direct persistent, server objects, sharing the same object key, type ID and POA name (For example, direct persistent, federated Naming Services). |
| Notes |
Please see the attached C demonstration, showing the problems that can arise if attempting to use the POA_Coloc interceptor with a mix of collocated and remote direct persistent, server objects, sharing the same object key, type ID and POA name. |
| Attachment | POA_Coloc.demonstration.zip |
#POA_Coloc
#KnowledgeDocs
#Orbix
