You mean, if I add headers using
axis2_options_set_http_headers(options, env, http_header_list);
I shouldn't have to free http_header_list?
That causes memory leaks in my application...
Hatim,
axis2_options_set_http_headers adds the header list as a property
and this list gets freed
axis2_svc_client_send_receive?
Is there going to be an API to free custom headers as well?
Thanks
-Original Message-
From: Danushka Menikkumbura [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 03, 2008 1:08 AM
To: Apache AXIS C Developers List
Subject: Re: Service client options to set custom
So if I use the new proposed interface to add a custom http header, how
will I free the custom headers (or all http headers) after
axis2_svc_client_send_receive?
Is there going to be an API to free custom headers as well?
Yes. We will have the following API calls.
/**
* Adds a
11:50 AM
To: Apache AXIS C Developers List
Subject: Re: Service client options to set custom HTTP headers
Hatim Daginawala wrote:
At what point will these headers get freed and who will be responsible
for freeing them?
Currently, I add http headers right before
axis2_svc_client_send_receive
, 2008 9:49 AM
To: Apache AXIS C Developers List
Subject: Re: Service client options to set custom HTTP headers
But then the user need to create axis2_http_header_t instances. Can we
use an string key value pair and covert them to the header type
internally
Message-
From: Danushka Menikkumbura [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2008 9:49 AM
To: Apache AXIS C Developers List
Subject: Re: Service client options to set custom HTTP headers
But then the user need to create axis2_http_header_t instances. Can we
.
thanks,
Damitha
Thanks
-Original Message-
From: Danushka Menikkumbura [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2008 9:49 AM
To: Apache AXIS C Developers List
Subject: Re: Service client options to set custom HTTP headers
But then the user need to create axis2_http_header_t
Hi Danushka,
override options come into play when we reuse operation client. Say
after sending some application messages you need to override some
options. Then you create new options struct and called svc client's
set_override_options. What happens is that existing options struct
becomes
override options come into play when we reuse operation client. Say
after sending some application messages you need to override some
options. Then you create new options struct and called svc client's
set_override_options. What happens is that existing options struct
becomes parent and your
Danushka Menikkumbura wrote:
Hi Devs,
There is a requirement to have support for custom HTTP headers in
Axis2/C. To do that we need to let the operation client know the
header details. One options is to set headers in service client
options and pass them on to operation client as the
So what is the option that you propose?
HTTP_HEADERS = array of (key = value) ?
An array of axis2_http_header_t*.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
Danushka Menikkumbura wrote:
So what is the option that you propose?
HTTP_HEADERS = array of (key = value) ?
An array of axis2_http_header_t*.
But then the user need to create axis2_http_header_t instances. Can we
use an string key value pair and covert them to the header type internally?
But then the user need to create axis2_http_header_t instances. Can we
use an string key value pair and covert them to the header type
internally?
No he doesn't have to. The interface call accepts the name and the value
and it in turn creates the header instance.
The interface call :
Hi Devs,
There is a requirement to have support for custom HTTP headers in
Axis2/C. To do that we need to let the operation client know the header
details. One options is to set headers in service client options and
pass them on to operation client as the operation client uses the
service
14 matches
Mail list logo
