hammant 02/01/01 15:43:59
Modified: armi PROPOSAL
Log:
Another proxy class generation idea.
Revision Changes Path
1.6 +7 -3 jakarta-commons-sandbox/armi/PROPOSAL
Index: PROPOSAL
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/armi/PROPOSAL,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- PROPOSAL 1 Jan 2002 23:25:56 -0000 1.5
+++ PROPOSAL 1 Jan 2002 23:43:59 -0000 1.6
@@ -82,13 +82,17 @@
1) BCEL for generated proxy class.
- The current impl writes java source then compiles it. We could do this
- inline with BCEL.
+ inline with BCEL. This as an heavier, but more design perfect
+ alternative to the current server side impl.
+
+2) Generated classes from getResource() from jars on the serverside as an
+ alternative to the byte arrays in the current server side impl.
-2) Startable API for Server
+3) Startable API for Server
- The server needs to implement and act upon start() and stop() APIs.
-3) unpublish() methods in Server.
+4) unpublish() methods in Server.
- The server needs to be able to unpublish a service. There is a
possibility that in conjuction with suspend()/resume() a service
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
