01 4:01 PM
To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: apache 1.3.12 and tomcat 3.3-m2 connection problem ??
Hello,
I'm currently using apache 1.3.12(mod_jk) and tomcat 3.3-m2
under solaris 2.6 talking ajp13
Everything works fine except that I encounter sometime an
Internal Server Error
Hello,
I'm currently using apache 1.3.12(mod_jk) and tomcat 3.3-m2 under solaris 2.6 talking
ajp13
Everything works fine except that I encounter sometime an Internal Server Error if I
don't restart Apache each time I restart tomcat. Is there a fix for that problem ?
On the other hand I use a
}
out.close();
}
}
You may use netscape as browser or ie if you don't care about waiting 15 pushes.
Thank you for your help.
-Original Message-
From: Jestin Jean-Francois
[mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 4:01 PM
To: '[EMAIL P
, 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
