Re: Using JERI over the internet
Gregg Wonderly <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Mark Brouwer wrote: > 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. From a practicle experience. SSH tunneling is equivalent to having a fully routable path. The added bit, of course, is that the security exposure/risks are minimized into the machines on both ends, rather than all machines on the network from a simple network connectivity perspective. We've talked about JXTA some in the past. Has anyone done anything more with the JXTA endpoint implementation that was announced on the list here? That's another form of tunneling, but probably doesn't provide an additional security controls/constraints? Gregg Wonderly -------------------------------------------------------------------------- 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]