axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kamlesh kumar <>
Subject AxisIOStream vs SoapTransport
Date Mon, 14 Aug 2006 16:51:25 GMT
I have created a very simple subtype of AxisIOStream
using std::stringstream.

However, the SoapDeSerializer and SoapSerializer api
for setting the input stream takes a SOAPTransport
instead of AxisIOStream. 

int setInputStream(SOAPTransport* pInputStream);

Can anyone tell me why does it take a SOAPTransport
and not a AxisIOStream ? 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. Let
me know if this is feasible or not ? 

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message