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 http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
