Donald Adams
7/22/2004 1:43:00 AM
The reason is for data transfer. I originally split the data and routed
through a webservice which allowed multi-threading for free (meaning I
didn't have to code it). But my customer asked for larger packets and
faster, so I tried remoting without going through IIS. I went from 1000
rows that took 2.5 seconds through IIS to 16000 rows (57MB) that took 2.9
seconds through remoting. However, my new solution is just single threaded
so I thought I'd ask about the IIS limit. "Hanging" the app. for this
amount of time is not a problem since it runs as a windows service. Using
IIS would also mean the customer wouldn't have to open up other ports.
Thanks for the tcp channel tip, that helped, but now I need to make sure I'm
using the sinkProvider params correctly.
Donald Adams
"Sunny" <sunny@newsgroups.nospam> wrote in message
news:uardQMzbEHA.2408@tk2msftngp13.phx.gbl...
> Hmm, never tried. If the object is hosted in IIS, then this limit most
> probably will be present.
>
> But, generally this is bad idea to pass 4MB data. As your question is
> about http and IIS, I assume that you are preparing something for
> internet use. The network can be slow, and from user perspective,
> hanging the application for more than 20-30 seconds without any progress
> indicator is not acceptable. I would redesign and see if I can separate
> the data in smaller chunks, so I can output something.
>
> Sunny
>
> In article <OlC4RysbEHA.596@TK2MSFTNGP11.phx.gbl>, BDA_2003@hotmail.com
> says...
> > Does Remoting using http have the IIS send packet limit of 4MB?
> >
> > Thanks in Advance,
> > Donald Adams
> >
> >
> >