Dante,
Any solution that you use is going to be custom, and will possibly
prohibit other platforms from using it (for example, Java, Unmanaged C++, VB
6). In these situations, you are going to have to code the proxies
individually (based on platform). This is a bad thing, IMO.
I would change the web service so that you don't transfer in one call.
Perhaps have a method indicating the beginning of a call (which returns a
token), and then make multiple calls to another method which would take the
data in chuncks (passing the token). Finally, you would call a third method
to indicate the end of the transfer, and to process the results.
Of course, you might not be concerned about interoperability, and you
are just using .NET on the client end. If this is the case, why use web
services? Why not use something a little more proprietary that would not
place these limitations on you? Of course, if you are concerned with
interoperability, then this paragraph doesn't apply.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Dante" <da*****@hotmail.com> wrote in message
news:ch**********@news.xmission.com...
I have developed a PHP web service that runs on a linux machine. I have
also developed a windows forms client to the web service in C#. The only
problem that I'm having is that the data that I send to the web service is
too large. For one, the server denies any post greater than 8 MB. It
also
takes forever to send that amount of data. I would like to figure out how
to compress the soap content and then have the server decompress it after
it
has received it.
Has anyone done this? Does anyone know of any good resources with
examples?
Thanks
Dante
