Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 91260 invoked from network); 29 Sep 2004 09:31:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 Sep 2004 09:31:45 -0000 Received: (qmail 81488 invoked by uid 500); 29 Sep 2004 09:30:08 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 81404 invoked by uid 500); 29 Sep 2004 09:30:07 -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 81256 invoked by uid 99); 29 Sep 2004 09:30:05 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [195.212.29.136] (HELO mtagate3.uk.ibm.com) (195.212.29.136) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 29 Sep 2004 02:30:02 -0700 Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id i8T9TwvH205006 for ; Wed, 29 Sep 2004 09:29:58 GMT Received: from d06ml063.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1307.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i8T9TuYv141164 for ; Wed, 29 Sep 2004 10:29:57 +0100 In-Reply-To: <20040929085004.51577.qmail@web40627.mail.yahoo.com> Subject: Re: Transport headers in Response To: "Apache AXIS C Developers List" Cc: Apache AXIS C Developers List X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Andrew Perry2 Date: Wed, 29 Sep 2004 10:33:13 +0100 X-MIMETrack: Serialize by Router on D06ML063/06/M/IBM(Release 6.51HF338 | June 21, 2004) at 29/09/2004 10:33:03 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I thought that the point of stubs was to keep things like transport away from the client so that the client just calls the service to get data but doesn't care how it's done, and certainly SOAP is supposed to be transport independent. From this perspective it does not make sense to allow access to the HTTP headers in the client, however useful it may be. Regards, Andrew Perry Clients for Web Service Stack perryan@uk.ibm.com Mail Point 127 IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN Tel. Internal 249828 External + 44 (0)1962 819828 Fax. + 44(0)1962 818080 Samisa Abeysinghe To Apache AXIS C Developers List 29/09/2004 09:50 cc Please respond to Subject "Apache AXIS C Transport headers in Response Developers List" 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