As revised 2006.05.04
Bionic Buffalo Tech Note #55
11. Objects to Be Implemented on Either the Client, or the Server, or Both
Objects with certain interfaces might be implemented on the client or on the server, depending on the
context and application. When implemented on the client, there is no expectation of invocation by any
server application. This section describes those client or server objects.
is an extension of the standard
service used in
most CORBA environments. As
is described in depth elsewhere, it will not be discussed
much here. This discussion will be limited mostly to the extensions.
will be implemented on the client for local client objects (as, for instance, if the
client has a local filesystem), and for objects downloaded from an object carousel. It will be
implemented on the server for objects residing on the server.
structure, which is different from a
represents one object (as with “colour/red”), a
may represent multiple
objects. Although there is no defined string representation for a
, we might imagine a
representation such as “colour/red,green,blue” to represent three objects named red, green, and blue.
defines various operations on a
corresponds roughly to a directory of objects, with each object bound to a name.
objects themselves, may be bound to names in other
s, resulting in directory trees. In
addition to the operations inherited from
four additional operations:
resolves the (possibly multiple) objects associated with a
deletes the resources associated with a reference to the
returns attribute values associated with the objects associated with a
sets attribute values associated with the objects associated with a
represents an ordinary file, with
operations. It will be
implemented on the client for local client files and for files downloaded from an object carousel. It will
be implemented on the server for files residing on the server.
represents streaming audio or video content. It includes methods to control playback:
object in a server is implemented on the server. The client must, of course, implement code
to handle the incoming data, but the
operations are implemented on the server object. A
single instance of a
object may handle multiple simultaneous client connections. (This is
unlike some nonDSMCC architectures which replicate a content object for each user.)
Copyright 2006 Bionic Buffalo. All rights reserved.
File tn0055; Modified 20060505 12:45:42
Page 16 of 20