summaryrefslogtreecommitdiff
path: root/TAO/examples/Content_Server/AMI_Observer/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/examples/Content_Server/AMI_Observer/README')
-rw-r--r--TAO/examples/Content_Server/AMI_Observer/README16
1 files changed, 9 insertions, 7 deletions
diff --git a/TAO/examples/Content_Server/AMI_Observer/README b/TAO/examples/Content_Server/AMI_Observer/README
index f9e4de33b5d..10d91d298f7 100644
--- a/TAO/examples/Content_Server/AMI_Observer/README
+++ b/TAO/examples/Content_Server/AMI_Observer/README
@@ -1,3 +1,5 @@
+$Id$
+
This program illustrates how to implement a simple client and server
using CORBA, IIOP, and asynchronous method invocations (AMI). Client
applications can use this service to download and display files from a
@@ -8,7 +10,7 @@ is as follows:
the Observer pattern. The server will ``push'' chunks of
data to the client. Thus, the client will play the role of
a ``server,'' as well.
-
+
* Operations in the IDL interface will use exceptions to propagate
problems back to clients.
@@ -75,7 +77,7 @@ the client receives all chunks of data in the proper order.
The client program performs the following activities:
-
+
1. From the command-line, it reads the name of the pathname
you want to download. It then initializes the client-side
ORB and uses resolve_initial_references() to obtain a
@@ -88,10 +90,10 @@ The client program performs the following activities:
called via the object reference to pass asynchronously pass
the Callback interface from the client to the server, which
then uses AMI to push chunks of the file to the client.
-
+
2. The server calls the sendc_next_chunk() method on the
- callback, passing in the offset and the next chunk.
-
+ callback, passing in the offset and the next chunk.
+
3. When the client receives the next_chunk() callback that
contains a chunk of the file, the contents are written into
a temporary file created in your a cache (e.g.,
@@ -99,8 +101,8 @@ The client program performs the following activities:
viewer is spawned to display the file. The type of viewer
to spawn is determined by examining the the content_type_
metadata returned by the server.
-
-
+
+
The example can be run as follows:
1. Start the Name Service: