[MOBY-guts] biomoby commit

Thu May 19 15:57:26 UTC 2005

senger
Thu May 19 11:57:26 EDT 2005
Update of /home/repository/moby/moby-live/Java/src/main/org/biomoby/shared
In directory pub.open-bio.org:/tmp/cvs-serv3891/src/main/org/biomoby/shared

Modified Files:
	package.html 
Log Message:


moby-live/Java/src/main/org/biomoby/shared package.html,1.1,1.2
===================================================================
RCS file: /home/repository/moby/moby-live/Java/src/main/org/biomoby/shared/package.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2

--- /home/repository/moby/moby-live/Java/src/main/org/biomoby/shared/package.html	2003/09/24 14:33:37	1.1
+++ /home/repository/moby/moby-live/Java/src/main/org/biomoby/shared/package.html	2005/05/19 15:57:26	1.2
@@ -3,15 +3,22 @@
 </head>
 
 <body>
-The components used by packages and classes developed for both
-Moby clients and (in the future) Moby servers.
-<p>
 
-The cornerstone piece is the interface {@link org.biomoby.shared.Central} that
-defines how to access Moby registry without any knowledge of
-the used transport protocol (SOAP, XML, etc.). This interface
-uses several "containers" representing pieces of the Moby mosaic -
-but most of them may not be necessary for the client.
-<p>
+It contains components that are used from more than one (other)
+packages. The bottom-line (or a bottom-rule) is: If one wants to run
+clients, it must be sufficent for him to pack all classes from {@link
+org.biomoby.client} and from this package only. If one wants to create
+a registry oriented component, it is enough for him to pack 
+<tt>org.biomoby.registry</tt> and this package.  And similarly for service
+providers which would pack <tt>org.biomoby.service</tt> and again this
+package.  <p>
+
+Additionally this is a good place for putting here Java interfaces -
+assuming that they are expected to be used more generally. The
+cornerstone piece is the interface {@link org.biomoby.shared.Central}
+that defines how to access Moby registry without any knowledge of the
+used transport protocol (SOAP, XML, etc.). This interface uses several
+<em>container</em> classes representing pieces of the Moby mosaic.
+
 
 </body> </html>


