Re: Clarification on firewall issues with Java networking APIs
- From: Arne Vajhøj <arne@xxxxxxxxxx>
- Date: Mon, 10 Dec 2007 19:41:49 -0500
Qu0ll wrote:
I understand that RMI doesn't play well with the internet because it can't work properly when either the client or the server is behind a proxy unless tunneling is used and that tunneling is slow and prevents callbacks from being used. So I get it that RMI is probably not the network API for me.
It is difficult but possible to get RMI through an opened port in
a firewall.
A proxy server that only knows HTTP seems as a total roadblock for
RMI to me.
And I understand that servlets don't have this problem because they communicate through the standard HTTP port
The proxy server understands HTTP and forward those. Note that in
most cases client/server via HTTP through proxy server will only
work if it is on the client side.
but that servlets don't support callbacks for non-HTML clients. (Feel free to disagree if appropriate).
It is not obvious to me what you mean with callbacks. But most
certainly the servlet does not care what type of client is requesting.
Which leads me back to NIO. Does it suffer the same problems as RMI? Namely, will it play well if the client is behind a proxy?
NIO is an API not a protocol.
Plain sockets (both normal and via NIO) will usually only be able
to go out through a proxy server if they emulate the HTTP protocol.
I you need something network allowable, then look for web services
(SOAP/HTTP).
Arne
.
- Follow-Ups:
- References:
- Prev by Date: Re: Compiler Options in NetBeans 6.0?
- Next by Date: Re: Symbolic benchmark
- Previous by thread: Clarification on firewall issues with Java networking APIs
- Next by thread: Re: Clarification on firewall issues with Java networking APIs
- Index(es):
Relevant Pages
|
