Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 19083 invoked from network); 30 May 2008 07:42:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2008 07:42:59 -0000 Received: (qmail 54374 invoked by uid 500); 30 May 2008 07:42:49 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 54344 invoked by uid 500); 30 May 2008 07:42:49 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 54333 invoked by uid 99); 30 May 2008 07:42:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2008 00:42:49 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sierk.schmittner@googlemail.com designates 209.85.198.243 as permitted sender) Received: from [209.85.198.243] (HELO rv-out-0708.google.com) (209.85.198.243) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2008 07:41:58 +0000 Received: by rv-out-0708.google.com with SMTP id c5so3523179rvf.24 for ; Fri, 30 May 2008 00:42:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=bsO4uC6Kp3HcCmIKlwBxHKQliGoXa54Le5vALDdjc4k=; b=eCxELGoMIAPzecz7fhntufoXdbRTl8Ulu0zu9+edA6/JCsuTyfiPmtOZde5s5LmS3FXk3mVuwbw5FSMzXkCUXg7tmygKQUGxDabvexXJRTXHtvp1uErioqcxwSJIO6GMEuNXz8rbLJtZefZka6K8bATppJ341Uu4k1icvsoT6zE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=SuRpv7H4WWlHBqv6ME/k7+Wu3QvAyzBAowycTel2683lyWhiqgSXWdzwfq4DvG38xsY7/kd5bKM0f1NV1GLvUcTA+geMpBQt3B6Z44YVBBdIiXAGzt/OeKLeidCfS3Vk1bvVQDW7MgIms0Jdz1zPZcHWTZbyr/RpYch+XOpoTPc= Received: by 10.141.141.3 with SMTP id t3mr2811375rvn.213.1212133334634; Fri, 30 May 2008 00:42:14 -0700 (PDT) Received: by 10.141.4.6 with HTTP; Fri, 30 May 2008 00:42:14 -0700 (PDT) Message-ID: <5b7e58560805300042y64f4a50fx73d6119f2a061c04@mail.gmail.com> Date: Fri, 30 May 2008 09:42:14 +0200 From: "Sierk Schmittner" To: "Tomcat Users List" Subject: Re: Server push with Tomcat 6/Comet In-Reply-To: <483EE416.1090203@hanik.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3305_5998227.1212133334609" References: <5b7e58560805290453t3aaa3f4p4fb6e9b8595e0776@mail.gmail.com> <483EE416.1090203@hanik.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_3305_5998227.1212133334609 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, > I am using a Comet-based servlet and I'm facing two problems: >> - When I write the data to the response's outputstream and call the flush >> method, the data is only send to the client when there is a minimum amount >> of bytes written on the outputstream. Is it possible to change this >> behavior >> so that the data is send immediately? >> > response.flushBuffer() ? I'm calling response.flushBuffer(), but the data is not received immidiately by the client, only when a certain amount of data is written. Is it possible that there is any connection to the packet size or some buffer? I am using the APR connector and tried to set the tcpNoDelay parameter to true, but it did not work. Have you any other idea? > - When the last task ist finished, its result should be send back to the >> client and the connection should be closed. Is it possible to terminate >> the >> connection on the server side? Or how can I trigger the Comet-End-Event? >> >> > there is a fix in tomcat/trunk SVN to allow async CometEvent.close event > waiting for the next 6.0.x release before I propose the backport So the fix will be in the next 6.0.x release? Is there a release date? Best regards, Sierk ------=_Part_3305_5998227.1212133334609--