[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] Re: JGroups ECF server
|
ok Scott, so if I get an ecftp:// server just behind an http server I can see you ?
2009/4/29 Scott Lewis
<slewis@xxxxxxxxxxxxxxxxx>
Hi Pierre,
Pierre Henry Perret wrote:
ok Scott,
but why if the JGroups knows about that ?
It's possible to config Jgroups as to be itself sort of... ECF JGroups server , wouldn't it ?
I"m not sure if I'm understanding you correctly, but the way the JGroups provider works is that when an ECF 'manager' is created (note it's not a 'server' in the traditional sense, so it's refered to as the pub/sub group 'manager'), it starts-up and listens to a multicast ip addres/port combination. Then, ECF client containers can connect to that group *iff* the connectivity (via multicast) is present...that is, if I start a group manager on ecf.eclipse.org, and then try to connect to it from here at my desk, the connection/communication will only work if the multicast messages sent from my process to the ECF group manager can make it...i.e. through all routers from my lan to ecf.eclipse.org. And this is not (at all) guaranteed on the wider internet (unfortunately, but that's a long story).
Scott
2009/4/29 Scott Lewis <slewis@xxxxxxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxxxxxx>>
Hi Pierre,
One thing to be aware of with the JGroups provider...if multicast
IP is used it's unlikely that such containers will be visible over
the Internet...and depending upon the network they may not even be
visible on the lan. It just depends upon the extent of support
for multicast.
Scott
Pierre Henry Perret wrote:
yes Remy, but I would like to test JGroups in a public container.
By the way, I dont mange connecting with Eclipse IM u sing my
BUg account, but I've verified this one connecting on my
gugZilla account without problem !
--
Pierre
------------------------------------------------------------------------
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
