in reply to Yet Another Stupid CGI Question

Not a direct answer to your question, but you probably don't want to return a page with a table with 1000+ rows in it. For one thing, you may kill some browsers. If it doesn't kill the browser, it'd probably take aeons to render it.

A better solution might be to return just a subset of the records (10, 25, or 50 are popular choices) and provide a means to page through the results (pass along an extra couple of paramters that are the chunk size and the current location in the result set).

Replies are listed 'Best First'.
Re: Meta-reply
by jepri (Parson) on Oct 19, 2001 at 16:43 UTC
    While your answer is neater I was recently forced by a client to return tables with hundreds of cells (against my advice). The entire page ran to greater than 80kb. It took about fifteen seconds to download over a modem but all modern browsers handled it fine. Netscape waits until the download is finished before it renders but that isn't too bad.

    The funny bit was where the client tried to blame me for the slow download speed.

    ____________________
    Jeremy
    I didn't believe in evil until I dated it.

[reply]

In Section Seekers of Perl Wisdom