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 (athena.apache.org: domain of pallewela@gmail.com
 designates 66.249.82.230 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=BmBgpzyupdGTPDKigoUnUOFHc9+kk2x7AvbLouR5VwXrQKjIk3ZjW1UzNWrfNISxTm4Hv26JeHIOYLt5BlItZhPifMTQr6HvH+PqoCl586aNCnjsjH9GfiliFJJOdJkD6kemxdu/71D5IFA+QDTabRX2kE5LQUsHWQQ4xzL/oRE=
Message-ID: <953017480802130044p4034a4e3maf505d4d5098a3a7@mail.gmail.com>
Date: Wed, 13 Feb 2008 14:14:33 +0530
From: "Dumindu Pallewela" <pallewela@gmail.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>,
 senaka@wso2.com
Subject: Re: Exposing Transport Headers to a Service
In-Reply-To: <59138.124.43.208.94.1202883943.squirrel@webmail8.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <36172.124.43.209.89.1202816743.squirrel@webmail8.pair.com>
	 <47B18A33.4050009@wso2.com>
	 <953017480802122115t706da39bpacfaed3d5259832d@mail.gmail.com>
	 <59138.124.43.208.94.1202883943.squirrel@webmail8.pair.com>

Hi Senaka,

> The decision should be made inside core_utils.c. I believe that it would
> be a great deal of hassle if we are to include it the axis2.xml, and
> propagate it to there. Also, if it is configurable, it should be a service
> level configuration. Therefore, I believe it is better to have this inside
> a #ifdef block. Therefore, the user will have to compile it allowing this
> functionality. Isn't that better? Also, this axis2.xml based filtering
> wouldn't be required, if the user wishes to use this he may simply use it,
> or just leave it as it is. It doesn't make any difference to our logic.

Yes it would be a hassle to use axis2.xml. And I am ok with using
#ifdef (as far as we provide the user some means of getting the job
done)

Only reason I wanted to see axis2.xml involved is that one day (one
fine day :)) some one will need to filter the headers that are sent to
the service, due to say security concerns. In such a situation, it
would be easier if we already have implemented this feature using
axis2.xml. Might be too futuristic though :)

>
> Regards,
> Senaka
>


-- 
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672

WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org