Actually sending it as XML and having the client render it using an XSL might make it much faster assuming the client does the transformation. IE does that, I'm not sure about the latest versions of Netscape.
The reason it takes so long is that the browser needs to make a lot of decisions and rendering calculations to figure out how to display the table "correctly." It can't do these until it's seen *ALL* of the data. For instance the width of the columns could be affected by the amount of text you have in the last row of your table. You don't need to use javascript to do this. AFAIK the XSLT should work out of the box. By the way, why do you need to handle this many rows? The only reason that I can think of that would justify this exercise is if you need to print a report. Dror On Fri, May 10, 2002 at 11:31:56AM -0400, Chen, Gin wrote: > Thanks for the many great inputs on this. > Just out of curiosity, perhaps the XML will help out a bit though. I also > have the data sent as a TSV (not file just String displayed with excel as > the content type) > and it displays MUCH faster than the HTML version. > But then to display it on the client side as useful text, I'll have to set > up with an XSL. Would the translation take as long or longer than the > current method of just sending HTML? Anyone have experience in the > performance of it this way with large amounts of data? > I know I can use javascript and client side translation of XML using the > Microsoft XSLT plugin but I have the restriction of not using any client > side installs. > Does anyone know a way to translate an XML clientside to HTML without using > a plugin? > > Thanks, > -Tim > > -----Original Message----- > From: Michael Weller [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 10, 2002 7:55 AM > To: [EMAIL PROTECTED] > Subject: Re: Large Table > > > hi! > i think this wouldn't speed up the displaying progess, because the client > still needs to download all the data before it can display it (and now > there's another step involved: the client-side xml rendering). > split the table up in multiple ones, so the client can display one small > table after the other. > > -mw > > ----- Original Message ----- > From: Silvio dos <mailto:[EMAIL PROTECTED]> Passos Neto > To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Sent: Friday, May 10, 2002 1:36 PM > Subject: Large Table > > Hi, > > If you can put the table data into a XML document, you'll can write the > table using a JavaScript to read the XML. Then, you will write the table on > client-side. > > Is it works? > > Silvio dos Passos Neto > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Webwork M�dia Interativa > -- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.zapatec.com ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
