axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Susantha Kumara" <susan...@opensource.lk>
Subject RE: SoapSerializer buffer allocation code is broken
Date Wed, 28 Jul 2004 10:04:45 GMT
Hi Alexei,

I applied your patch and found that server side is working fine. But I
cannot commit the code until I fix the problem with client transport. I
am looking in to it and will commit the code once I fix it.

Thanks a lot for the patch.

Susantha.
---
> -----Original Message-----
> From: Alexei Dets [mailto:adets@idsk.com]
> Sent: Wednesday, July 28, 2004 5:00 AM
> To: Apache AXIS C Developers List
> Subject: Re: SoapSerializer buffer allocation code is broken
> 
> Hi!
> On Tuesday 27 July 2004 00:19, damitha kumarage wrote:
> > I think we need to get rid of this double buffering thing. Axis C++
do
> 
> I'm attaching the patch to SoapSerializer class that completely
eliminates
> the
> buffering and all code associated with it (callback functions etc.).
This
> fixes the problem of the long strings output from the server - it is
not
> crashing it anymore.
> 
> However, it is not possible to use Axis C++ client to receive these
> strings,
> it catches an exception: "AxisTransportException:Transport buffer is
> empty".
> Axis Java or PHP nuSOAP clients work fine. I suspect that transport
layer
> are
> using some buffers in the manner similiar to SoapSerializer and also
> suffer
> from some type of buffer overflow problems. I'll try to find the
problem.
> 
> 	Alexei


Mime
View raw message