PYTH — Python Issue: Dynamic Skeleton Interface

Section 1.5.2 describes the "repository_id" parameter passed to
PortableServer.DynamicImplementation.invoke as specifying the interface type
for which the operation was called.

How is the ORB able to deterimine this information? Does this really make
sense anyway? Is it the repository id of the most derived interface or for
the current call?

There is no document describing what (if any) operations are ORB provided on
PortableServer.DynamicImplementation. For example, it makes sense to provide
default implementations of the following operations:

• _is_a
• _get_interface
• _get_domain_managers

Also, does it make sense to have the programmer over-ride a "_repository_id"
or "_most_derived_interface" operation on this class in order to generate
object references which don't require the client to invoke "_is_a" on (in
order to narrow the reference)? Otherwise most calls to a python
DynamicImplementation would result in the client always invoking _is_a in
order to narrow.

The observation is correct, the ORB cannot supply the repository_id. Specifying that the servant mus