- From: <sn@bigmac.neopoly.de>
- Date: Mon, 16 Aug 1999 20:37:06 +0200
- To: www-talk@w3.org
- Cc: sn@bigmac.neopoly.de
Hello,
I'm trying to use HTTP as the protocol for an interactive application
that I'm developing. A java applet ("client") needs to exchange data
with a server.
I need to use HTTP so the applet can be used behind corporate firewalls
using HTTP Proxies.
The client must be able to receive messages (events) from the
server as soon as they happen, so there needs to be an open connection
at all times (I don't want to do polling). The current model
I have in mind is using two connections: One for sending data to the
client (always connected, tunneled in a GET request), one for sending
data to the server (opened if there is data to be sent and closed
afterwards).
I've studied the HTTP/1.1 spec (RFC 2616) for better ways to do this.
Persistent connections (keep-alive) come to mind, but it seems the
popular browsers will happily use multiple connections whenever they like
to and the java applet has no control over this. I need to use java's
java.net.URLConnection class so I can use the browser's proxy (if any),
otherwise this would not be a problem.
Any ideas/suggestions/experiences?
Best regards,
-Sven Neuhaus
Received on Monday, 16 August 1999 14:37:17 UTC