You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by db...@apache.org on 2012/01/20 23:21:02 UTC

svn commit: r1234187 - /openejb/site/trunk/content/ejb-refs.mdtext

Author: dblevins
Date: Fri Jan 20 22:21:02 2012
New Revision: 1234187

URL: http://svn.apache.org/viewvc?rev=1234187&view=rev
Log:
improved description of discovery

Modified:
    openejb/site/trunk/content/ejb-refs.mdtext

Modified: openejb/site/trunk/content/ejb-refs.mdtext
URL: http://svn.apache.org/viewvc/openejb/site/trunk/content/ejb-refs.mdtext?rev=1234187&r1=1234186&r2=1234187&view=diff
==============================================================================
--- openejb/site/trunk/content/ejb-refs.mdtext (original)
+++ openejb/site/trunk/content/ejb-refs.mdtext Fri Jan 20 22:21:02 2012
@@ -164,7 +164,8 @@ If say, there are two servers that have 
 
 In the event that the `ejbd://192.168.1.20:4201` server cannot be contacted, the second server will be tried.
 
-See these docs for more details on Failover and Discovery:
+This sort of arangement can also happen dynamicall against a list of servers that continuously grows and shrinks.  The server list is maintained behind
+the scenes using server discovery logic that can function on either UDP or TCP.  See these docs for more details on Failover and Discovery:
 
  - [Multicast Discovery (UDP)](multicast-discovery.html)
  - [Multipoint Discovery (TCP)](multipoint-discovery.html)