Return-Path: Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: (qmail 20464 invoked from network); 11 May 2010 19:21:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 May 2010 19:21:50 -0000 Received: (qmail 56228 invoked by uid 500); 11 May 2010 19:21:50 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 56204 invoked by uid 500); 11 May 2010 19:21:50 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 56196 invoked by uid 99); 11 May 2010 19:21:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 May 2010 19:21:50 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eklinger@gmail.com designates 74.125.83.173 as permitted sender) Received: from [74.125.83.173] (HELO mail-pv0-f173.google.com) (74.125.83.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 May 2010 19:21:42 +0000 Received: by pvg12 with SMTP id 12so34816pvg.32 for ; Tue, 11 May 2010 12:21:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=5eR2WiRaodgEET6x6+l9Yg5rfqQ+6Lc0nowyBtK/a0A=; b=WdK8itkpEc0CqFhLh6R2ZmNyL7AvkoJC+dJz/YiLc5uzK5qGocAjyCGL+pBy6M8Loc r3eNgJb8U6oAYF4xR/pp3QJJ78iQYmWrzrWHA+YykefMevvhYp9I18HdtcYBLVlwBB8Q f9COVpazzLjHZs2IYkYBQDXukOnzw5llYqdvM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rzs5mkScYfBtVD2VX6jCZtpjmCi3yGHPb24vk7bZYk0CsssEYOjY6aZd0ZvO1Jz2yt up1QzsGFI5boN8qwaaaype89d1vzP6KFBHorKR6O+i8vKt7IaT+1tjsi7zjLg7la6kd+ 5TbtwQKts/n0wjiEZtKGtxEnVytI3GlMXAecc= MIME-Version: 1.0 Received: by 10.115.39.8 with SMTP id r8mr4829361waj.228.1273605681372; Tue, 11 May 2010 12:21:21 -0700 (PDT) Received: by 10.115.88.2 with HTTP; Tue, 11 May 2010 12:21:21 -0700 (PDT) Date: Tue, 11 May 2010 12:21:21 -0700 Message-ID: Subject: Multi-threaded Services From: Evan Klinger To: c-user@axis.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hello, When developing a REST service in Axis2/C, how does Apache handle the integration with the Axis2 module? When a request comes in that is passed to the Axis2 module, does each request create a new instance of the service or is it a new thread? Basically, in the service we may need to open a file for writing but also for reading, depending upon the request. However, we don't want to read while the file is being written to so it seems like we need a rw lock/mutex, but that will only work if the service is called by multiple threads. If they are called from separate processes then I don't think this approach will work. Any information on how to handle this would be greatly appreciated. Thank you Evan --------------------------------------------------------------------- To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org For additional commands, e-mail: c-user-help@axis.apache.org