Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 11578 invoked from network); 28 Jul 2009 11:53:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Jul 2009 11:53:54 -0000 Received: (qmail 6515 invoked by uid 500); 28 Jul 2009 11:55:11 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 6448 invoked by uid 500); 28 Jul 2009 11:55:10 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 6438 invoked by uid 99); 28 Jul 2009 11:55:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 11:55:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 11:55:00 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MVlGR-0007Ei-Q1 for modules-dev@httpd.apache.org; Tue, 28 Jul 2009 04:54:39 -0700 Message-ID: <24697873.post@talk.nabble.com> Date: Tue, 28 Jul 2009 04:54:39 -0700 (PDT) From: ricardo13 To: modules-dev@httpd.apache.org Subject: Re: Threads In-Reply-To: <1404e5910907280404i614b055esb495a77530a15273@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ricardoogrande@gmail.com References: <24697041.post@talk.nabble.com> <1404e5910907280404i614b055esb495a77530a15273@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I thought better and I think that first thread will be delete. Because, all post_request_read() hook, I add request, dont need a thread for it. Now, second thread's "asynchnous". That means, doesn't need a event "add request" for scheduling. It's independent. I didn't undestand about "talk to your thread standalone". What do I will talk for thread ? Thank you Ricardo Eric Covener wrote: > > On Tue, Jul 28, 2009 at 6:59 AM, ricardo13 > wrote: >> >> Hi, >> >> I'm using Worker MPM and would like to implement a module that uses 2 >> threads and one array. >> The first thread works adding requests in array. Just it. >> And second thread schedules requests in array to processing. >> >> I used post_config() hook for initialize structures and creates threads. >> What hook do I use for threads ?? Because if I initialize in post_config, >> how thread run after post_request_read and before content generator ?? > > You can't have your dedicated thread directly "invoked" during the > apache hooks. > > You need to write normal methods that will be invoked by the normal > request-processing threads, and talk to your standalone thread via > some type of non-Apache-specific IPC. > > -- > Eric Covener > covener@gmail.com > > -- View this message in context: http://www.nabble.com/Threads-tp24697041p24697873.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.