> Hello,
>
> I need to stream data from a "DataTable" to the client's machine. The
> data first need to be converted to .CSV , and ziped before streaming
> it to the client.
Rendering to CSV is pretty staright-forward.
How important is it to zip it? Must the user download datafile.zip containing
data.csv ?
If it's "just" for performance of transferring a large amount of data, it
might be a
lot easier to apply http compression which all modern browsers support.
Just set the metabase attribute DoDynamicCompression for your GenerateCSV.aspx
page -
more details on msdn.
> Does anyone has any experience with this? Any code snippet will be
> very welcome.
>
> Many thanks in advance
>
> Cheers
Smith - 30 Aug 2007 15:17 GMT
> > Hello,
> > I need to stream data from a "DataTable" to the client's machine. The
> > data first need to be converted to .CSV , and ziped before streaming
> > it to the client.
> Rendering to CSV is pretty staright-forward.
> How important is it to zip it? Must the user download datafile.zip
> containing
> data.csv ?
Yes
> If it's "just" for performance of transferring a large amount of data, it
> might be a
> lot easier to apply http compression which all modern browsers support.
This sounds very interesting. Yes the problem here is performance. The file
could be more then gigabyte. Is HTTP compression losseless?
Do I get the same order of compression as with zip? How is the file
uncompressed on the client side?
> Just set the metabase attribute DoDynamicCompression for your
> GenerateCSV.aspx
> page -
> more details on msdn.
> > Does anyone has any experience with this? Any code snippet will be
> > very welcome.
> > Many thanks in advance
> > Cheers
Many thanks
S
Smith - 30 Aug 2007 15:17 GMT
> > Hello,
> > I need to stream data from a "DataTable" to the client's machine. The
> > data first need to be converted to .CSV , and ziped before streaming
> > it to the client.
> Rendering to CSV is pretty staright-forward.
> How important is it to zip it? Must the user download datafile.zip
> containing
> data.csv ?
Yes
> If it's "just" for performance of transferring a large amount of data, it
> might be a
> lot easier to apply http compression which all modern browsers support.
This sounds very interesting. Yes the problem here is performance. The file
could be more then gigabyte. Is HTTP compression losseless?
Do I get the same order of compression as with zip? How is the file
uncompressed on the client side?
> Just set the metabase attribute DoDynamicCompression for your
> GenerateCSV.aspx
> page -
> more details on msdn.
> > Does anyone has any experience with this? Any code snippet will be
> > very welcome.
> > Many thanks in advance
> > Cheers
Many thanks
S
Hello Smith,
I'd like just add a note to Neils post, that there is http://weblogs.asp.net/owscott/archive/2004/01/12/57916.aspx
a good description how to set the gzip compression on the IIS
WBR,
Michael Nemtsev [.NET MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
> Hello,
>
[quoted text clipped - 8 lines]
>
> Cheers
Hi Smith,
Here is a sample app that does precisely that.
http://www.nicecleanexample.com/ViewApp.aspx?TID=aspdotnet_csv
HTH
John
> Hello,
>
[quoted text clipped - 8 lines]
>
> Cheers