Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of damitha23@gmail.com designates
 64.233.184.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding;
        b=OuUGQY6w8JuYrA+wFrTsra5DWc1bXoZoOqRfqUeI6s7H5GgZ7xZCQfA5HDWV8xzBd9SdtAAI69hyMqgQabf+0bIN3RMoG8h48FkOb70lZ5kg5aLzqC9LSHszJUKpKR9S3GgYTkOiM8dvgF7Of6ujsQQ0TznCU9i09U2xlPAThHc=
Message-ID: <446B013C.9040500@gmail.com>
Date: Wed, 17 May 2006 16:55:56 +0600
From: Damitha Kumarage <damitha23@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
MIME-Version: 1.0
To: axis-c-dev@ws.apache.org
Subject: [Axis2]  A Memory handling strategy.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,
There are schenarios where we set void pointers and the receivers of 
these void pointers
have no way of freeing the memory associated with them.

We faced that problem yesterday when paramter attributes needed to be 
set in axis2_param_t.
axis2_param_t belong to util project. So we cannot have om dependancies 
in axis2_param when
it wants to free om attributes.

To handle this situation I introduced a new class called 
axis2_generic_obj_t.
We can set the concerned type(or void pointer) as value there in and at 
the same time
set the freeing function there in. So when someone free the 
axis2_generic_obj_t object instance it
will call the call back free function from within and free the set value.

If you have any concerns about this strategy please let's discuss

thanks
Damitha