axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kamlesh (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Created: (AXISCPP-992) AxisIOStream vs SoapTransport ( Removing transport specific stuff from SoapSerializer and SoapDeSerializer)
Date Thu, 17 Aug 2006 00:39:13 GMT
AxisIOStream vs SoapTransport ( Removing transport specific stuff from SoapSerializer and SoapDeSerializer)
-----------------------------------------------------------------------------------------------------------

                 Key: AXISCPP-992
                 URL: http://issues.apache.org/jira/browse/AXISCPP-992
             Project: Axis-C++
          Issue Type: Improvement
            Reporter: kamlesh


The SoapDeSerializer and SoapSerializer api
 for setting the stream takes a SOAPTransport
 instead of AxisIOStream. 
 For ex:
 int setInputStream(SOAPTransport* pInputStream);
 
Could it be refactored to take a AxisIOStream instead ?
It would be nice if the  transport specific stuff is handled outside of the
 serializer and deserializer in a separate class. This would allow anyone to easily implement
a sub-type of AxisIOStream and pass it to the serializer and deserialer( for instance I have
a custom AxisIOStream based on stringstream, however I can't use it since the serializer and
deserializer take a SoapTransport)

Let  me know if this is feasible or not ? 


 

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message