[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Is ECF Discovery Service necessary when using RemoteServices

> -----Original Message-----
> From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Markus Alexander Kuppe
> Sent: Friday, January 14, 2011 3:31 PM
> To: ecf-dev@xxxxxxxxxxx
> Subject: Re: [ecf-dev] Is ECF Discovery Service necessary when using
> RemoteServices
> On 01/14/2011 02:59 PM, Bartosz CzerwiÅski wrote:
> >> With this approach you would essentially have to retrieve all remote
> >> services from the remote container and add them manually to the local
> >> service registry. Pretty much what ECF remote services gives you for
> >> free anyway if used with ECF discovery.
> > Maybe you can help with the zoodiscovery container. When using
> "zoodiscovery.flavor.centralized" flavour of zoodiscovery I encounter
> problems with the "root node". According to the description located on the
> http://wiki.eclipse.org/Zoodiscovery page there should be one node which is
> connecting to itself. Doing this that way it causes that the node cannot
> connect and it's generating "Attempt connecting to ..." log entry all the time.
> How does your network topology look like? Are both consumer and provider
> located in the same LAN/subnet, or are they in different ones?
The same subnet. Tested on both loopback and local interface. Firewall is disabled. What if they would be in the different subnets - would zoodiscovery protocol be eligible?

> Markus
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev

Attachment: smime.p7s
Description: S/MIME cryptographic signature