Stephen McConnell wrote:
This is a proposal for the restructuring of the instrumentation suite:
Current structure:
instrument
instrument-manager
instrument-client
Proposed structure:
instrument <-- no change
instrument-manger <-- move AltRMI classes to
instrument-monitor/altrmi/server
instrument-monitor
- altrmi/server <-- two classes from instrument manageer
- altrmi/client <-- content of instrument-client
Any objections?
The only concern I have is that the Client and the Manager (i.e.
the client and server) portions using the AltRMI transport will
be largely duplicated code between RMI implementations, SOAP
implementations, SNMP implementations, etc.
The important thing -- if you want to abstract out the transport
is to seprate out the AltRMI specific portions:
On Manager, it is two classes--all in their own package.
On Client, I would have to check, but I estimate that it is
very similar.
Leif did a good job of separating out the transport--at least
on the server side/manager side.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
