You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Sergio Gomes <se...@fedeltapos.com> on 2015/06/04 03:58:57 UTC

Apacher River over Internet

Hi, I have an client/server application using Apache River using the
BasicJeriExporter over tcp/ip. Now I have a requirement to use it across
the Internet (currently using local network). How could be it done? I saw
Apache River can communicate using IIOP, would it be a good approach? Has
someone tried to use Apache River over IIOP?

Thank you.

Re: Apacher River over Internet

Posted by Patricia Shanahan <pa...@acm.org>.
Could you perhaps write and put on the web site a short "best practices" 
article on this?

On 6/5/2015 6:08 AM, Gregg Wonderly wrote:
> Across the internet, you loose access to multi-cast only discovery.
> So, your client must use unicast and the service must advertise/join
> a unicast capable lookup service (Reggie).   I’ve used Jini across
> long distance network paths for quite some time, and it works just
> fine as long as you use unicast (direct IP addresses).  For outside
> of an intranet access to an intranet lookup service and then for
> access to the discovered service, you will need to take firewall
> configuration into account most likely.  Port forwarding will be
> required if there is an networking barriers such as NATing routers
> etc.
>
> Gregg
>
>> On Jun 3, 2015, at 8:58 PM, Sergio Gomes
>> <se...@fedeltapos.com> wrote:
>>
>> Hi, I have an client/server application using Apache River using
>> the BasicJeriExporter over tcp/ip. Now I have a requirement to use
>> it across the Internet (currently using local network). How could
>> be it done? I saw Apache River can communicate using IIOP, would it
>> be a good approach? Has someone tried to use Apache River over
>> IIOP?
>>
>> Thank you.
>

Re: Apacher River over Internet

Posted by Gregg Wonderly <gr...@gmail.com>.
Across the internet, you loose access to multi-cast only discovery.  So, your client must use unicast and the service must advertise/join a unicast capable lookup service (Reggie).   I’ve used Jini across long distance network paths for quite some time, and it works just fine as long as you use unicast (direct IP addresses).  For outside of an intranet access to an intranet lookup service and then for access to the discovered service, you will need to take firewall configuration into account most likely.  Port forwarding will be required if there is an networking barriers such as NATing routers etc.

Gregg

> On Jun 3, 2015, at 8:58 PM, Sergio Gomes <se...@fedeltapos.com> wrote:
> 
> Hi, I have an client/server application using Apache River using the
> BasicJeriExporter over tcp/ip. Now I have a requirement to use it across
> the Internet (currently using local network). How could be it done? I saw
> Apache River can communicate using IIOP, would it be a good approach? Has
> someone tried to use Apache River over IIOP?
> 
> Thank you.


Re: Apacher River over Internet

Posted by Gerard Fulton <cg...@gmail.com>.
One potential approach is to create a service that registers a proxy that
is capable of communicating across networks.

On Wed, Jun 3, 2015 at 6:58 PM, Sergio Gomes <se...@fedeltapos.com>
wrote:

> Hi, I have an client/server application using Apache River using the
> BasicJeriExporter over tcp/ip. Now I have a requirement to use it across
> the Internet (currently using local network). How could be it done? I saw
> Apache River can communicate using IIOP, would it be a good approach? Has
> someone tried to use Apache River over IIOP?
>
> Thank you.
>