ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Nichol <snicholn...@scottnichol.com>
Subject Re: SOAPTransport.receive()
Date Mon, 11 Nov 2002 17:07:09 GMT
I would like to see an analysis of the whole code path for reading the
response to see all the redundancies in processing.  I think that when
MIME attachment handling was added, there was an opportunity to remove
or restructure code that was not seized.

At the same time, I am worried about changing existing interfaces that
would break people's code.

Scott Nichol

----- Original Message -----
From: "Pavel Ausianik" <Pavel_Ausianik@epam.com>
To: <soap-dev@xml.apache.org>
Sent: Monday, November 11, 2002 11:34 AM
Subject: SOAPTransport.receive()


> Hello,
>
> I have found that we have interface SOAPTransport with method  public
> BufferedReader receive ();
>
> All three known implementations of SOAPTransport use following code
for this
>
> String s = .... // Create a Envelope String
> BufferedReader reader = new BufferedReader(new StringReader())
>
>
> ....
>
> in = st.receive();
> payloadStr = IOUtils.getStringFromReader(in);
>
>
> So we get a good transformation from String to String using at least
two
> Readers, and big enough buffers.   The code is used on each Call
> I think It worth to change interface and all usage to  public String
receive
> ().
>
> What do you think?
>
> Pavel
>
>
>
> --
> To unsubscribe, e-mail:   <mailto:soap-dev-unsubscribe@xml.apache.org>
> For additional commands, e-mail: <mailto:soap-dev-help@xml.apache.org>
>
>


Mime
View raw message