Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!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:27:00 -0600 Lines: 28 Message-ID: References: <10nfa5ogfbi9n$.1bfhtk130g1fr.dlg@40tude.net> X-Trace: individual.net KSLSyj6WwyCdooZq/hOjdQjSHPitjoQcoFZZcGTy1JzpC2CcMl Cancel-Lock: sha1:wKA9LfgcCecP4W1/CYKdwAUZEu8= 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:20112 I said (again): > 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 ??? Hi Denis: Put another 'alert()' in my page (just after the tag) , and determined that the new big page arrives back at the client very quickly (<0.5 secs), and then the fixed/frozen page is reverted to the *original* page while the new bigger page is being unravelled/digested --- approx seven seconds to do this 'onload' stuff ! Wow ! -Mel