--- Julia Lerman <[EMAIL PROTECTED]> wrote: > Beware that the webclient class, which has fileupload and filedownload > methods currently does not support FTP, though it will in Whidbey.
Good point. I'll just add a couple of points I thought of while skimming the posts. FTP is almost always a poor choice for file transfer. There was some reference to the idea that the protocol might be more efficient than other techniques, and that is simply not the case. Beyond that- - authentication is always in clear text unless you can control both endpoints and use a different product support alternate transports like ssl or ssh - data packets have the same issue - AFAIK ftp has no support to byte range requests which have been used in http downloads by clients to support robust recovery in the event of lost connections I would also say that a ~3mb file transfer may not be worth the effort to compress, thought the task is certainly made easier with the previously mentioned tools that support the web server initiated compression Two options not discussed or given much thought I think I worth considering. - simple xml over http without soap. That ~3mb request is not really enhanced by packaging up in soap envelopes is it? Could the url provide the context for the request? - try webdav which is the file oriented mechanism for http Philip - http://blogs.xcskiwinn.org/panmanphil "There's a difference between righteous anger and just being crabby" - Barbara =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
