Ice Study Notes 3: Object Adapter

A communicator contains one or more object adapters. an Object Adapter sits at
the boundary between the ice run time and the server application code and has a
Number of responsibilities:
• It maps ice objects to servants for incoming requests and dispatches the
requests to the application code in each servant (that is, an Object Adapter
implements an up-call interface that connects the ice run time and the application
code in the server ).
• it assists in life cycle operations so ice objects and servants can be created and
existing destroyed without race conditions.
• It provides one or more transport endpoints. clients access the ice objects
provided by the adapter via those endpoints. (it is also possible to create an
Object Adapter without endpoints. in this case the adapter is used for Bidirectional
callbacks-see section 36.7 .)

A communication device contains one or more object adapters. The Object Adapter is in ice run time
There are some responsibilities on the line between server and server:
• It maps the ice object to the servant of the incoming request and distributes the request to
ApplicationCode(That is, the Object Adapter implements an upward call interface
Run Time is connected with the application code on the server ).
• It assists in lifecycle operations so that ice objects and servant do not output
Current competition.
• It provides one or more transmission endpoints. The customer uses these endpoints to access the ice provided by the adapter
Object (it is also possible to create an adapter without an endpoint. Such an adapter is often used for callback-see section 36.7)

Each Object Adapter has one or more servants that incarnate ice objects, as well
One or more transport endpoints. If an Object Adapter has more than one endpoint,
All servants registered with that adapter respond to incoming requests on any
32.4 object adapters 797
The endpoints. In other words, if an Object Adapter has multiple transport
Endpoints, those endpoints represent alternative communication paths to the same
Set of objects (for example, via different transports ).
Each Object Adapter belongs to exactly one communicator (but a single
Communicator can have jsonobject adapters). Each Object Adapter has a name
That distinguishes it from all other object adapters in the same communicator.
Each Object Adapter can optionally have its own thread pool, enabled via
<Adapter-Name>. threadpool. Size property (see section 32.9.1). If so,
Client invocations for that adapter are dispatched in a thread taken from
Adapter's thread pool instead of using a thread from the communicator's server
Thread Pool.

Each Object Adapter has one or more servant to reflect the ice object.
There is one or more transmission endpoints. If the Object Adapter has more than one transmission endpoint, all
Servant registered with this adapter can respond to incoming requests on any endpoint. Change
If the Object Adapter has multiple transport endpoints, these endpoints represent accessing the same group
Different communication paths of objects (for example, through different transmission mechanisms ).

Each Object Adapter belongs to only one communication device (but one communication device can have multiple objects
Adapter. Each adapter has a name that distinguishes it from other adapters of the same communication device)

Each Object Adapter can have its own thread pool unforcibly.
<Adapter-Name>. threadpool. Size attribute to use this feature (see section 32.9.1
). If this feature is used,
The threads in the thread pool of the adapter, instead of the threads in the server thread pool of the communicator.