
Signature
HTH
Christoph Schittko [MVP, XmlInsider]
Software Architect, .NET Mentor
Thanks for replying!
The main problem is that I have a webservice method that
takes a xmldocument as a parameter. it works well, but
when that document is huge like 5 MB, I get this error:
The underlying connection was closed: An unexpected error
occurred on a receive.
I tried to change the size of the request in
machine.config, but no change! So my solution was to break
that xml file into something the web service can handle
and make multiples calls.
>-----Original Message-----
>The least memory intensive solution would be to read over the source
[quoted text clipped - 43 lines]
>
>.
Vadim Chekan - 21 Nov 2003 03:35 GMT
> Thanks for replying!
>
[quoted text clipped - 9 lines]
> that xml file into something the web service can handle
> and make multiples calls.
And you'll have another problem: you'll have to store chunks somwhere to
give them out on request.
Than for some reasons client can make request, pick up the first portion
of data, and don't request other ones, for fail reson, quit application,
connection problem, etc. So your temporary storage will grow with
garbage information.
Then you'll have to match somehow user session id with chunks set, and
you'll have to figure out somehow which chunk is going to be next.
Than you'll have to join chunks on client.
Aha, and how client will know either there are more chunks to retrieve?
Looks ugly.
You'd better spend some time on tracing and optimizing application.
5Mb shouldn't be so performance killing.
Vadim Chekan.
Christoph Schittko [MVP] - 28 Nov 2003 22:00 GMT
What exactly did you change in machine.config. Did you make all the changes
outlined in [0]?

Signature
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor
[0] http://www.dotnet247.com/247reference/msgs/7/36455.asp
> Thanks for replying!
>
[quoted text clipped - 66 lines]
> >
> >.