Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 79162 invoked from network); 15 Oct 2008 06:52:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Oct 2008 06:52:27 -0000 Received: (qmail 75095 invoked by uid 500); 15 Oct 2008 06:52:28 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 75085 invoked by uid 500); 15 Oct 2008 06:52:27 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 75074 invoked by uid 99); 15 Oct 2008 06:52:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Oct 2008 23:52:27 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.9] (HELO relay00.pair.com) (209.68.5.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 15 Oct 2008 06:51:20 +0000 Received: (qmail 29225 invoked from network); 15 Oct 2008 06:51:53 -0000 Received: from 202.129.232.129 (HELO ?10.201.2.159?) (202.129.232.129) by relay00.pair.com with SMTP; 15 Oct 2008 06:51:53 -0000 X-pair-Authenticated: 202.129.232.129 Message-ID: <48F5930A.2070206@wso2.com> Date: Wed, 15 Oct 2008 12:21:54 +0530 From: Danushka Menikkumbura User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: axis-c-dev@ws.apache.org Subject: Properties in Configuration Context Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Devs, We have been using the base context of conf_ctx to keep custom properties. What we normally do is, get the base context and use its (axis2_ctx) API to set/get properties. And we use external mutexes for synchronization. Why don't we have get/set calls in conf_ctx API itself so that we can set/get properties without any hassle. And that way we can use the mutex in conf_ctx to handle synchronization. I think that is the cleaner way of accessing the base. Any thoughts? Danushka --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org