Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 87693 invoked by uid 500); 27 Mar 2001 07:46:46 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 87683 invoked from network); 27 Mar 2001 07:46:46 -0000 Message-ID: <361024C34A6DD2118689006097AE2B4D0102C95C@css4.cs> From: GOMEZ Henri To: tomcat-dev@jakarta.apache.org Subject: RE: apache 1.3.12 and tomcat 3.3-m2 connection problem ?? Date: Tue, 27 Mar 2001 09:46:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N >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 also very interesting ! >It's look like another dilemma ;-) >But >>>>BTW, I'll see where the problem could be in mod_jk ;-) >Could you give me more information about the problem ? Argh, damn't english, I wanted to say I'll looking for where the problem could be in mod_jk. But as you know Apache add also timeout to requests