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 (hermes.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <04de01c4a648$685789c0$8b7b3009@LANKABOOK>
From: "Sanjiva Weerawarana" <sanjiva@opensource.lk>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
References: <20040929085004.51577.qmail@web40627.mail.yahoo.com>
Subject: Re: Transport headers in Response
Date: Wed, 29 Sep 2004 23:18:55 +0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Don't we need to in order to implement HTTP sessions (cookies)?
I remember implementing that for Apache SOAP many years ago ...

Sanjiva.

----- Original Message ----- 
From: "Samisa Abeysinghe" <samisa_abeysinghe@yahoo.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Wednesday, September 29, 2004 2:50 PM
Subject: Transport headers in Response


> Hi All,
>     The client transport implementations that we have at the moment do not
care about the
> incomming transport headers; they are just discarded.
>     We could easily capture the incomming HTTP headers in the response.
However, my question is,
> should we allow the Stub class to access these HTTP heades in the respose?
(does it make sense?)
>     If the above is required, we may have to update the current API for
the stub class.
> Thanks,
> Samisa...
>
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>