users@shoal.java.net

Re: [Shoal-Users] Advice about JXTA, HTTP and sub-nets...

From: Shreedhar Ganapathy <Shreedhar.Ganapathy_at_Sun.COM>
Date: Mon, 30 Jun 2008 12:29:51 -0700

Hi David
Some responses below:
David Taylor wrote:
> Hi!
>
> We're at the next stage in our evaluation of Shoal/JXTA and are now trying
> to gather data about sub-net communication.
>
> There seem to be two basic questions/concerns:
>
> 1. Can JXTA allow communication across sub-nets and through firewalls
> using *ONLY* the HTTP port? We are often told that all other ports are
> blocked and only port 80 (HTTP) can be used. This will be a total
> show-stopper unless we can find a way to do this.
>
Jxta supports this in my understanding. However, Shoal uses TCP based
support in Jxta for cross subnet communication. I am not sure if the
Http based support provides NIO support as in Jxta's TCP implementation.

Mo can probably answer this.

That said, I have a higher level question on your topology. Are you
using Shoal for communications between remote clients and a Shoal
cluster? In other words would your clients outside the firewall be
members of a Shoal cluster?

Or is your topology such that Shoal is purely used for cluster level
communications while your http traffic is with remote clients. In the
latter case, ideally you can configure Shoal communications on redundant
NICs that are part of an internal network while other redundant nics
service your client requests on an external network. This isolates Shoal
traffic for internal network such as cluster lifecycle eventing,
messaging between members, etc. while allowing client communications to
scale on a different network. This external network will typically be
fronted by a firewall with port 80 opened for traffic.
> 2. Assuming that we can use the HTTP port, how "busy" is JXTA. Again,
> we are often asked how much traffic is going to be caused by our
> application. Has anyone done any work on studying this?
>
If the above mentioned topology is feasible this part of your worries
could be lower. Shoal messaging through Jxta is for discovery,
healthmonitoring (periodic heartbeats), and app level messaging. You can
contact me offline to discuss your use case in detail if thats more
comfortable. I can bring in more people from here to the discussion if
need be.

Thanks
Shreedhar

> Thanks in advance.
>
> David
> --
> David W. Taylor
> Developer | SL Corporation | http://www.sl.com
> david.taylor_at_sl.com | Tel: +1.415.927.8555 | Fax: +1.415.927.8401
> ________________________________
>
> Email communication may contain privileged or confidential information
> proprietary to SL Corporation. If you have received this communication in
> error, we ask that you advise the sender by reply e-mail and immediately
> delete the message and any attachments without copying or disclosing the
> contents.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_shoal.dev.java.net
> For additional commands, e-mail: users-help_at_shoal.dev.java.net
>
>