You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by st...@apache.org on 2003/06/19 06:52:28 UTC
cvs commit: xml-axis/addons/discovery/doc ws-discovery.dbk
stevel 2003/06/18 21:52:28
Modified: addons/discovery/doc ws-discovery.dbk
Log:
bit more on discovery
Revision Changes Path
1.2 +9 -1 xml-axis/addons/discovery/doc/ws-discovery.dbk
Index: ws-discovery.dbk
===================================================================
RCS file: /home/cvs/xml-axis/addons/discovery/doc/ws-discovery.dbk,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ws-discovery.dbk 21 Apr 2003 05:28:01 -0000 1.1
+++ ws-discovery.dbk 19 Jun 2003 04:52:28 -0000 1.2
@@ -87,7 +87,12 @@
an endpoint being valid, and thus the limit of its cacheability.
Again, caching is an effective way to scale, and scoping could be
convenient to prevent accidental binding to the wrong
- implementation.</para>
+ implementation. The protocol includes some DHCP integration, the
+ idea being that services should receive scope information from the
+ DHCP service -devices autoscope themselves from the network. of
+ course, if the network does not provide scope, then the service is
+ unscoped.
+ </para>
<para>SLP addresses scalability with advertising of directory
servers, and a URL based query mechanism to specify searches on the
@@ -96,6 +101,9 @@
effectively create an emergent directory of all located devices,
which current UDDI implementations do not.</para>
+ <para>
+ Scoping is essential for scalability.
+ </para>
<para>What may be an interesting project would be to provide a UDDI
interface to a network of self-advertising web services; letting
programs use UDDI interfaces to find services in a dynamic network.</para>