RE: download/upload compression

Thread: RE: download/upload compression

Search this list only Search all lists
RE: download/upload compression
United States	2007-12-06 23:36:57

Hmmm, the client component doesn̵7;t necessarily have to use ADO, but it’s an easy way to stream xml back to the server AFTER the original file has been compressed. This can be done other ways, mainly however, compressing the file by creating an activex and applet to do the work is relatively easy, saves a ton of bandwidth whereas not compressing it before it’s uploaded means the client waits and the bandwidth is huge if you have any traffic at all since these are fairly hefty sizes. fwiw, Tom Mallard Software Design - Architecture Consumer Product Design From: Tim Curtin [mailto:tjc_tekhotmail.com] Sent: Thursday, December 06, 2007 6:37 AM To: aspnetaspadvice.com Subject: [aspnet] RE: download/upload compression There are a few things that will be happening: 1. Client will be uploading text files for ETL via the web browser fileupload control. 2. Client will be uploading large report files 3. Client will click on a report file for download. Can't use ADO as this needs to be cross browser. 1. Web Server 1 is in DMZ and page will leave file there.  Windows Service on Web Server 1 will periodically check for files and upload files to Web Server 2 Web Service behind firewall. 2. User will click on a file name on Web Server 1. Page will connect to another DisplayFile.aspx page via window.open() that will connect to Web Server 2 Web Service for the Byte[] array and set the MimeType to display the document.     Looking to compress the file during #2 download or perhaps 'chunk' the file during upload/download to the web page and web service. I've been googling and I've seen a couple of code samples where an HTTPModule is created to chunk the data imported to disk and override ASP.Net's full memory usage. From: johnjwarner.com To: aspnetaspadvice.com Subject: [aspnet] RE: download/upload compression Date: Thu, 6 Dec 2007 05:53:58 -0500 Just so I’m fully up on the discussion, are the files coming from a client (say like me out in the internet) to your webserver 1? Is this the file transfer you are concerned with? Is the concern about moving the files from your webserver 1 in the DMZ to your Intranet Server 2 behind the DMZ/Firewall? For client to webserver 1 have you considered just plain old ftp? It is old tired and proven and designed for just this sort of thing. The clients will have it on their computer. IE has it built in, Windows has a command line version (likely not an option with most people you will be dealing with). To use IE the user just types in ftp://your_url John Warner From: tomm [mailto:timallardmsn.com] Sent: Thursday, December 06, 2007 12:10 AM To: aspnetaspadvice.com Subject: [aspnet] RE: download/upload compression Tim, consider the idea of compression before uploading anything. Can recommend using ado/xml streaming for the file content, byte[] works well with this. Downside is client has to download the activex control and VB runtime for ADO. Our files were in the 60-80 Mb range most of the time with some hitting 150Mb but traffic is moderate so it’s still a big load. Most of these were images so compress well. Add memory to your servers, you don’t want them to use paging to disk from memory being maxed out. Tom Mallard Software Design - Architecture Consumer Product Design From: Tim Curtin [mailto:tjc_tekhotmail.com] Sent: Wednesday, December 05, 2007 11:04 AM To: aspnetaspadvice.com Subject:** [aspnet] download/upload compression Hello folks, We have a requirement to upload/download files as much as 100's of megs in size.  We're discussing the property topology.  Se below   DMZ --------- Web Server 1 Behind firewall ---------------- Web Server 2 File Archive Server SQL Server   1. Web Server 1 in DMZ for upload and temp storing of file 2. windows service on web server 1 that calls Web Server 2 behind firewall and uploads file asynchronously. 3. Web Server 2 exposes a web service to upload a byte[] and store on FileServer 1 as well as authentication/authorization functionality. WebService takes full byte[] and writes a file to a prescribed folder to either be ETL'd into a database or other files to be stored on the server for reading/downloading later.   Question: We're looking at building a proof of concept for uploading a large file and not flood the ASPNet process.  Have any of you overcome large file sizes and how did you do it?   Thanks much   Tim Share life as it happens with the new Windows Live. Share now! --- List Settings --- http://aspadvice.com/lists/ --- List Settings --- http://aspadvice.com/lists/ --- List Settings --- http://aspadvice.com/lists/ Connect and share in new ways with Windows Live. Connect now! --- List Settings --- http://aspadvice.com/lists/ --- List Settings --- http://aspadvice.com/lists/

[1]

about | contact Other archives ( Real Estate discussion Medical topics )