IIS + BinaryFormatter + LOTS of data
- From: pdxfilter-google@xxxxxxxxx
- Date: 19 Oct 2005 11:29:06 -0700
We need to transfer a large amount of data (100MB+) in a remoting
scenario using IIS and BinaryFormatter. The typical endpoints would be
T1 on the server and DSL/Cable on the client.
As an alternative, we'd considered having the server write a file out
to webspace (HTTP or FTP) and getting it via a more conventional HTTP
GET. This is still an option, but not ideal for us.
In an ideal situation, we would have something like:
byte[] GetTheData(); // Returns 100MB of data
Haven't done any testing, but my gut says this is a bad idea. Is there
a practical limit (timeouts, etc.) on the amount of data that can be
exchanged in one remoting call when using IIS? Reliability across a
range of clients is more important to us than raw speed.
We could do something like:
int ByteCount();
byte[] GetSomeData(int offset, int length);
....and get the data in chunks. This would allow a progress bar. How
big could we safely make the chunks?
Thanks for any input on this. I'm sure someone has tackled a similar
problem!
Jon
.
- Prev by Date: Remoting callback
- Next by Date: Remoted Object's connection status?
- Previous by thread: Remoting callback
- Next by thread: Remoted Object's connection status?
- Index(es):
Relevant Pages
|
