Spreadsheet XMLData property vs Export method performance issues

M

Mike

We are using the spreadsheet component in an asp.net web page to
display and update data which is posted back to the web server and
saved in the database. Our spreadsheet xml data size can be quite large
and range from 5 to 30 Mb. It can take up to 4 minutes when extracting
the xml data into client side memory for posting back to the web server
using the XMLData property of the spreadsheet, but if we use the Export
method to save the same data to a file on the client side disk, it only
takes about 5 seconds. Unfortunately, due to web browser security
restrictions, we can't access the saved file, read it back, and post it
to the web server as a work-around for the XMLData performance issues.

Why is there such a huge performance difference between the two ways of
extracting data? Is there a way to optimize the performance when
calling the XMLData property (using CSVData instead is not possible for
us), or is there a way to intercept the Export method stream before it
saves the file and use that to post to the web server?

Any help or other ideas are greatly appreciated!
Thanks, Mike.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top