Right now in our WSE 2 we're using DIME. DIME is fine for downloads, uploads
on the other hand are a pain in the a.s because of the DIME limit and IIS
limits.
Now I'm switching to WSE 3 + MTOM and I've read all over the place that it's
reliable for very large files. Great, but what about HTTP based web services
on IIS? Am I going to have to change anything on the IIS server to make it
do more than 4 meg files??
Should I stick with chunking? (yukky mess)
Thanks,
James Hancock
Yep, you'll have to add the following to your configfile:
<configuration>
<system.web>
<httpRuntime maxMessageLength="409600"/>
</system.web>
</configuration>
ms-help://MS.WSE30.1033/WSE3.0/html/4344d43e-ceb4-43a9-8f8c-6a3f89f786bd.htm
However, if I was you, I stick with chuncking, or rather MTOM and chuncking,
since it only seems to be possible to stream data from server to client, and
not the other way around.
Regards,
Søren
> Right now in our WSE 2 we're using DIME. DIME is fine for downloads,
> uploads on the other hand are a pain in the a.s because of the DIME limit
[quoted text clipped - 9 lines]
> Thanks,
> James Hancock
James Hancock - 27 Mar 2006 05:55 GMT
It would be fine if all I had to do was update my web.config. What I'm
concerned about is that IIS is going to do what it did with DIME and kill it
with > 4meg uploads regardless of what you set in your web.config unless you
go and edit the machine.config file, which isn't acceptable.
Have you tested uploads with IIS > 4 megs? Has anyone?
> Yep, you'll have to add the following to your configfile:
>
[quoted text clipped - 27 lines]
>> Thanks,
>> James Hancock