Re: Using JERI over the internet

Mark Brouwer <[email protected]>
Newsgroups gmane.comp.java.sun.jini
Message-ID <[email protected]>
Nati Shalom wrote:
> Hi Mark
>
> "Could you tell more about the various constraints you are confronted
> with such as HTTP(S) only, whether the Jini servers are routable from
> the client perspective, etc."
>
> At this point there not too many constraints i.e. we can use standard
> http and handle our own authentication on top of that.
>
> WRT to callback that's another issue I came across the following
> reference which uses SSH tunneling:
> http://www.javaranch.com/newsletter/200311/Journal200311.jsp#a3
>
> Have anyone tried it?
>
> It sounds simpler approach that can also handle callbacks if it works?

Yes, tunneling can work, in that case you don't even have to use an HTTP
based transport. I've done that in the past for very simple things. If
you control both ends (infrastructure) most of the times you can work
your way around depending on security requirements.

But I wouldn't call it a simpler approach, my experience is that you
have to configure the host and port number for your endpoints in a way
that they only work from the other end of the tunnel. You might use a
custom socket factory though that uses a different IP address when
initiating a connection based on the network the proxy resides but my
experience is that when you solve one thing you often break another.

When you have a complete picture of the locations where your clients and
services are located and an idea about the number of clients you
probably can manage.
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.