As revised 2006.05.04
Bionic Buffalo Tech Note #55
10. Objects to Be Implemented on the Server
Objects with certain interfaces are expected to be implemented on the server (service provider) device.
Client (service consumer) applications at a remote device invoke methods on these objects using the
remote ORB, which along with the server ORB and an intervening GIOP connection, mediates the
requests. It is possible, of course, for server applications to invoke operations on those server objects
locally, without involving the network. This section describes those server objects.
is used when the UN session protocol is not used. It provides the
operations required by a client implementation of
reference, and possibly
a reference to a first service, and may indicate that certain objects must be downloaded for the session to
provides remote directory operations to a client
object when the UN session protocol is employed.
provides remote directory operations, as well as
, to a client
object when the UN session protocol is not
implements the server end of the download protocol, with RPC being used to
carry the control information.
is an alternative interface for a directory or database. It allows queries on the content using
a minimal subset of SQL.
is a service used to manage the interfaces of objects in a DSMCC system. It is a
kind of management frontend for the interface repository defined by CORBA. Four operations are
defined on this interface:
returns certain information about an interface, including the IDL defining the interface
defines new interfaces and type definitions
verifies the coherency of the interface repository
removes a definition from the repository
Unlike standard CORBA, DSMCC assigns numeric identifiers to all interface and type definitions in
the repository. The
interface supports the use of these numeric identifiers.
Copyright 2006 Bionic Buffalo. All rights reserved.
File tn0055; Modified 20060505 12:45:42
Page 15 of 20