hammant 01/12/29 16:48:41
Modified: armi PROPOSAL README.txt
Log:
Updated instructions for new server->client pasing of proxy class definitions.
Revision Changes Path
1.3 +8 -7 jakarta-commons-sandbox/armi/PROPOSAL
Index: PROPOSAL
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/armi/PROPOSAL,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PROPOSAL 30 Dec 2001 00:42:10 -0000 1.2
+++ PROPOSAL 30 Dec 2001 00:48:41 -0000 1.3
@@ -37,6 +37,12 @@
- ARMI can be build easily into any application or application framework.
Individual aspects can be reimplemented (overridden) as the need arises.
+5) Choice of location of generated Proxy class.
+
+ - Classes providing client side implementation of the transported
+ interface(s) can be either on the client side or the server side (and
+ duly transported) at time of lookup.
+
Limitations:
1) Pass by value only.
@@ -44,13 +50,8 @@
- Unlike proper RMI, ARMI only currently supports "pass by value". If
an argument or return type were another ARMI published service, then
it could not currently be handled by ARMI. (to fix).
-
-2) Generated "stubs" have to be in the client VM.
-
- - Later we will allow server to pass forward implementation class
- definitions as opposed to just newInstance() them as at present.
-
-3) This is not of any use for EJB Home/Remote interfaces. The container
+
+2) This is not of any use for EJB Home/Remote interfaces. The container
maker chooses the transport for use that container, not the bean coder.
This is intended for other client server solutions.
1.2 +9 -6 jakarta-commons-sandbox/armi/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/armi/README.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.txt 29 Dec 2001 01:35:22 -0000 1.1
+++ README.txt 30 Dec 2001 00:48:41 -0000 1.2
@@ -11,21 +11,24 @@
To test ObjectStream over Socket transport:
- In DOS shell #1 - "ant -buildfile test.xml test1-serve"
- In DOS shell #2 - "ant -buildfile test.xml test1-client"
+ In DOS shell #1 - "ant -buildfile test.xml test1a-serve"
+ In DOS shell #2 - "ant -buildfile test.xml test1a-client"
To test ObjectStream Piped transport
- In DOS shell #1 - "ant -buildfile test.xml test2"
+ In DOS shell #1 - "ant -buildfile test.xml test2a"
To test (Armi over) RMI transport:
- In DOS shell #1 - "ant -buildfile test.xml test3-serve"
- In DOS shell #2 - "ant -buildfile test.xml test3-client"
+ In DOS shell #1 - "ant -buildfile test.xml test3a-serve"
+ In DOS shell #2 - "ant -buildfile test.xml test3a-client"
To test Direct transport
- In DOS shell #1 - "ant -buildfile test.xml test4"
+ In DOS shell #1 - "ant -buildfile test.xml test4a"
+
+To test with class definition forwarding (from server to client),
+same as above four tests, but with "b" instead of "a" in the target name.
o Use in your application
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
