[AXISCPP-992] AxisIOStream vs SoapTransport ( Removing transport specific stuff from SoapSerializer and SoapDeSerializer)

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Basic Architecture
• Assignee: Unassigned
• Reporter: kamlesh
• Created: 17/Aug/06 00:38
• Updated: 22/May/08 00:07

Description

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 ?