Re: [Wonder-disc] multicast change notification

[Mike S. <ms...@md...>]

OK ... Try this on.  Basically you just need to turn on coordinator  
pool and enable synchronizer, and that's it (assuming you only have  
one application running on your network).  I'm tempted to make  
multicast group not have a default so you can't accidentally deploy  
two applications on the same group.  It would not fail fast, and it  
would fail in a pretty confusing way (i.e. an exception because some  
random Entity from another application could not be found).

######################################################################## 
#
# ERX Multicast Synchronizer
######################################################################## 
#
## To use multicast synchronization, you must turn on the
## ERXObjectStoreCoordinatorPool.  Just setting it to 1 is enough to
## allow things to work.
#er.extensions.ERXObjectStoreCoordinatorPool.maxCoordinators=1

## Enables multicast synchronization (required in addition to  
ERXObjectStoreCoordinatorPool).
#er.extensions.multicastSynchronizer.enabled=true

## (Optional) The local bind address defines the network interface  
that will be used
## to transmit and receive multicast messages.  If not set, multicast  
synchronizer
## will use WOApplication.application().hostAddress().  If you want  
to run outside
## of a WOApplication, you should set this value explicitly.
#er.extensions.multicastSynchronizer.localBindAddress=

## (Optional) If you want to set a specific identifier for this  
member of this
## multicast group, you can set a six byte hex string here.  If you  
do not set
## this value, it will be automatically assigned based on the bind  
address and
## the WOApplication.application().port() value.  If you want to run  
outside
## of a WOApplication, you should set this value explicitly.
#er.extensions.multicastSynchronizer.identifier=0a6400f113f9

## (Optional) This address defines the multicast group address that  
all the instances
## will join.  The default value is 230.0.0.1 if you do not set  
this.  The multicast
## group is similar to defining a "chat room".  Any application that  
joins this
## group will send and receive messages to eachother.  Generally,  
each application
## that you deploy should set its own multicast synchronizer group.   
If you do not
## explicitly set this value, all of your applications will talk to  
eachother, even
## if they do not share a common set of EOModels, which will lead to  
exceptions, and
## possibly global thermonuclear war.
#er.extensions.multicastSynchronizer.group=230.0.0.1

## (Optional) The port number is the port that will be used to send  
multicast messages
## over.  The default value is 9753.
#er.extensions.multicastSynchronizer.port=9753

## (Optional) A comma separated list of entities to multicast  
synchronize.  The
## default is to not set this, which translates into "include all  
entities".
#er.extensions.multicastSynchronizer.includeEntities=

## (Optional) A comma separated list of entities to NOT multicast  
synchronize.  The
## default is to not set this, which translates into "exclude no  
entities".
#er.extensions.multicastSynchronizer.excludeEntities=

## (Optional) A comma separated list of host names that are allowed  
to multicast
## change notifications.  The default is to not set this, which  
translates into
## "allow all hosts."  If your network is not secure, not setting  
this list
## leaves you vulnerable to an DoS-style attack where anyone could  
notify your
## multicast group of EOGlobalID changes.
#er.extensions.multicastSynchronizer.whitelist=

## (Optional) The maximum size of a datagram packet that we can  
send.  Defaults
## to 1024.
#er.extensions.multicastSynchronizer.maxPacketSize=1024

On Dec 11, 2006, at 11:23 AM, Anjo Krank wrote:

> Actually, I meant the IP from the WOApp... app.hostAddress 
> ().getHostAddress(). If that is localhost, then you're probably not  
> deploying anyway...
>
> Am 11.12.2006 um 17:14 schrieb Mike Schrag:
>
>> If anyone knows how to construct a
>> wildcard socket and then find out what interface it actually bound
>> to, let me know.
>