Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 97678 invoked from network); 7 Jan 2010 09:18:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Jan 2010 09:18:48 -0000 Received: (qmail 93546 invoked by uid 500); 7 Jan 2010 09:18:45 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 93436 invoked by uid 500); 7 Jan 2010 09:18:44 -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 93425 invoked by uid 99); 7 Jan 2010 09:18:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2010 09:18:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.147.97.3] (HELO web63108.mail.re1.yahoo.com) (69.147.97.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 07 Jan 2010 09:18:36 +0000 Received: (qmail 81916 invoked by uid 60001); 7 Jan 2010 09:18:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1262855894; bh=I85FmWmiBG1RBk7eZMDn3V2elP/N4gnOWryzwkJcHiI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=DiNeyjvA9EikwJ6thQwbpvkySa8Dq9OuwUOwmUVWjVse3gN3zSlVjRIWKf/UUwM9/auoCeaqN1rQoFI42WiUziRQQ6TyLB2Kv/NN0JhQ92kFV0HvGb8sbBQXJgwzTmnpBy1fZpI+1ZS9KZ6k6KgVUs3H4nmY7K8Xu2XNrzjAaeM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Gpd7UTOxwtn8LtNR1bkZC03TvADbl2M0gqhyDnQtgbGQRSS0002KyMIksRm2uwXVhFravOBT7qz3Kqf8U5oUc5GBSfW1icAWtNruNwHZIEU/6j+FELaSgrlFwqIfxBQft3vrX9LtOen4ytw05w3/8MdNCGOWwNPWffAAXYRP/mk=; Message-ID: <942817.81069.qm@web63108.mail.re1.yahoo.com> X-YMail-OSG: IAYXEw8VM1nr0QTME2fUDnpsRSosMB_Qg6HnZk1ha0UvEryh2qqqHR2xaL6IoWVA8islqVA3q8xMG_J0tMIG55g3FK.L0F8rJ.Z7LOcbwF5sacPINDu5y2OQKTYBFbdd11gtLlwa9aH_4nBj88jJ1odDTAWK00ASgeQ5oE5mAalbIh8_p2DDOUnW2DhdyJBREw_l.tEbSXWItEFNiSnTWhbufflRu1EeV7sVvGY6CKtdkbsKisz6eSLBbK32fWx7JkVQ1xEZt13ivty649YMfeOAHCBRmwVSEXvvwICx3aH1COsQf62AnADw3Af3crNTdrs8RcpmRZxsNl4JF5wUiaavJeS_0lRhjhzY.j8O Received: from [98.248.177.54] by web63108.mail.re1.yahoo.com via HTTP; Thu, 07 Jan 2010 01:18:14 PST X-Mailer: YahooMailClassic/9.0.20 YahooMailWebService/0.8.100.260964 Date: Thu, 7 Jan 2010 01:18:14 -0800 (PST) From: Bob Hall Subject: RE: Comet and thread binding To: Tomcat Users List In-Reply-To: <27056330.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- On Thu, 1/7/10 at 12:02 AM, tbee wrote: > > Yes. But the problem with comet is that it may switch > threads "mid request"; > a request can be suspended, the thread freed up, and after > a while the > request is resumed, but by probably a different thread. So > I cannot bind the > request to the thread anymore. I don't have much Comet experience but given that it can pause and resume processing of a given request, would it be possible to bind your execution context to that 'request' and re-bind it to the 'new' Thread when request processing resumes? - Bob --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org