summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornaga <naga@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-01-30 04:55:21 +0000
committernaga <naga@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-01-30 04:55:21 +0000
commit906b1b477e46acb9594271b52e562695369aadb1 (patch)
tree3f849c9ece6142da1ee2aedab053984785ded970
parent0386d0f2fb5c635b707a879e114ecf93ad24928d (diff)
downloadATCD-906b1b477e46acb9594271b52e562695369aadb1.tar.gz
Default_Servant/README added
-rw-r--r--TAO/tests/POA/Default_Servant/README45
1 files changed, 45 insertions, 0 deletions
diff --git a/TAO/tests/POA/Default_Servant/README b/TAO/tests/POA/Default_Servant/README
new file mode 100644
index 00000000000..d64c59dbe80
--- /dev/null
+++ b/TAO/tests/POA/Default_Servant/README
@@ -0,0 +1,45 @@
+// $Id$
+
+
+Default_Servants
+================
+
+ By using the USE_DEFAULT_SERVANT policy, the developer can create
+ a POA that will use a single servant to implement all of its objects.
+ This approach is useful when there is very little data associated
+ with each object, so little that the data can be encoded in the
+ Object Id.
+
+Example:
+=======
+ In the example implementation a Single Servant is enough to
+ serve requests for a File Descriptor interface. The Object Id of the
+ Descriptor objects are formed from the file handle returned by the
+ System call. The servant can get the file handle from the object
+ reference to process the request. Thus a single Descriptor servant
+ can serve multiple objects.
+
+SERVER:
+======
+
+ 1. To run the server, type
+
+ % server [-ORBport port] [-ORBobjrefstyle URL] [-ORBhost host]
+
+CLIENT:
+======
+ The client tries to create a file "test" and writes a message to
+ the file and reads it back and prints it.
+
+ 1. To run the client, type
+
+ % client -k IOR
+
+ where the IOR is got from the server output.
+
+
+
+
+
+
+