Berin Loritsch wrote:

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.


As things stand - yes - at least on the client side.  As you stated, the
instrument manager has a nice seperation but things are not so elegant
on the client - that's why I suggested the expidient route of repackaging
the client as the AltRMI client monitor.  This would give us (Leif?) some
more time to refactor the transport indepednent aspects into a real
instrument client package.



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.


The minimum approach is to simply explude the alt rmi classes from the instruemnt manager jar and build a seperate jar container the two classes. This at lteast would enable seperation of jar depedencies.


On Client, I would have to check, but I estimate that it is very similar.


I've browsed around with the idea of putting in place a IIOP solution however what I saw on the client was not seperated (as per the server). Leif's recent message is clarifying some things that suggest the sitution if better than my initial assesment (classes not used etc.).


Leif did a good job of separating out the transport--at least on the server side/manager side.


I agree.

Cheers, Steve.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to