Could you send us the pushlet code example.
I could help here (mod_jk) :-)
"Entre truands, les bnfices, a se partage, la rclusion, a
s'additionne."
-- Michel Audiard
-Original Message-
From: Jestin Jean-Francois
[mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 4:01 PM
To:
here are 2 articles speaking about the pushlet
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet-2.html
here is a very simple sample pushlet :
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
, March 26, 2001 5:34 PM
To: '[EMAIL PROTECTED]'
Subject: RE: apache 1.3.12 and tomcat 3.3-m2 connection problem ??
here are 2 articles speaking about the pushlet
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet-2.
--- Jestin Jean-Francois
[EMAIL PROTECTED] wrote:
here are 2 articles speaking about the pushlet
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet-2.html
here is a very simple sample pushlet :
{
public
, March 26, 2001 6:10 PM
To: [EMAIL PROTECTED]
Subject: RE: apache 1.3.12 and tomcat 3.3-m2 connection problem ??
Hi,
I take a look at pushlet and find it very bad design.
Using opened http connections to do real-time job is
not realist.
In that case you keep an :
- one OS (
I agree the idea of the pushlet is a bit confusing because it
uses http (a non real time protocol) to do pseudo real-time job,
but real-time is always more "hungry" than other technology
(think about streaming !! ).
On the other hand having pseudo real-time monitoring over
standard http is
