Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Mel Smith" Newsgroups: comp.lang.javascript Subject: Re: .submit(....) problem Date: Sat, 1 Jun 2013 17:10:32 -0600 Lines: 25 Message-ID: References: <10nfa5ogfbi9n$.1bfhtk130g1fr.dlg@40tude.net> X-Trace: individual.net hnyeM4a2lohygTw/gb2YMg51xRBG8jmd8FuYB6nOUxnBYRw/KM Cancel-Lock: sha1:nT0ysBOZBB+Wcl3fEX8DsmDfy88= X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Xref: csiph.com comp.lang.javascript:20111 I said: > Unfortunately No . I build the whole page (sometimes up to 382K) > inside my CGI app. When it is completely assembled, I output it at once > to my Apache 2.2.22 server. I will 'time' the building in my cgi app, and > see how long it taks to receive, assemble, and send -- I'll let you know > Hi Denis: I just put a timer in my cgi app. For my largest file (approx 382K), it takes only 0.33 seconds from the time I receive the original
elements (i.e., the POST) until I output and pass the rebuilt and re-assembled page (382K) to Apache for compression. Then, does that mean that the 'reception' and 'unravelling' of this new big page back at the client causes it to *first* revert to the original page before displaying the new (much bigger) page ??? Thanks for commenting. -Mel