axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (AXISCPP-63) Improve client side HTTP transport
Date Tue, 27 Apr 2004 09:23:53 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-63

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-63
    Summary: Improve client side HTTP transport
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
 Components: 
             Transport (Client)
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Sevwandi Abeysinghe

    Created: Tue, 27 Apr 2004 2:23 AM
    Updated: Tue, 27 Apr 2004 2:23 AM
Environment: All platforms

Description:
When trying to set HTTP headers from the C++ stub it was found that it does not support the
current Axis C++.

>From the discussions on the mailing treads, this solution was found.
If we can have the two API functions to set transport properties

int Call::SetExtraTransportProperty (const char* key, const char* value)

int Call::SetTransportProperty (AXIS_TRANSPORT_INFORMATION_TYPE type,
const char* value) the problem is solved.

Also we might need to have corresponding get functions,

const char* Call::GetExtraTransportProperty (const char* key) const char* Call::GetTransportProperty
(AXIS_TRANSPORT_INFORMATION_TYPE type)

The wsdl2ws tool generated code will use the appropriate function(s) to set any properties
that are in the wsdl.

Also any transport specific handlers too can use these same API functions to set/get transport
properties.

Extension of the transport layer is planned in the TO DO list :
See : http://nagoya.apache.org/wiki/apachewiki.cgi?AxisCpp_TODO


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message