Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #20109

Re: .submit(....) problem

From "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups comp.lang.javascript
Subject Re: .submit(....) problem
Date 2013-06-01 16:50 -0600
Message-ID <b0vc54FfkjnU1@mid.individual.net> (permalink)
References <b0sf2kFqspvU1@mid.individual.net><XnsA1D1F205F7AB0eejj99@194.109.133.133> <b0stobFtsg1U1@mid.individual.net><b0tcrbF24eiU1@mid.individual.net><10nfa5ogfbi9n$.1bfhtk130g1fr.dlg@40tude.net><b0uh19F9n1kU1@mid.individual.net> <kodo1n$iff$1@dont-email.me>

Show all headers | View raw


Denis said:
> This probably falls over because your server starts sending the new page
> before it has finished assembling it - as soon as the browser gets part
> of the new page, it clears out the old one and starts to display what
> it's received so far of the new one.

    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

>
>>     Now, serendipitously,  by using gzip (i.e., mod_deflate) in my
>>     Apache
>> Server, this *does now* happen.
>
> That's probably because using compressed pages, your server doesn't start
> the compression until the whole page/file is prepared, so it doesn't send
> the page until it's been fully created.
>
> The more complete solution in your server side script might be not to
> send any non-header content until you have finished preparing the page.


    As noted above, I follow the same procedure in my CGI server app, and 
when the page is built and complete, I output it to Apache where it is 
(assumedly) 'gzipped' and then is sent off to the client.

    So, I'm still perplexed.

    But, what I see on my client's screen (which is really *me* testing) is 
my final content I wish left in place, but displayed only for a 
split-second, then the screen reverting to the original screen, then a long 
wait, then the new screen displays.

    So, it is between the 'submit' and the reception that something happens 
to revert to the original screen during the wait process..

    I'll have to take this to bed with me again and hope I get an 
inspiration.

Thanks for the comment.

-Mel

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

.submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-05-31 14:21 -0600
  Re: .submit(....) problem "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-05-31 23:47 +0200
    Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-05-31 18:32 -0600
      Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-05-31 22:49 -0600
        Re: .submit(....) problem JJ <duh@nah.meh> - 2013-06-01 14:18 +0700
          Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 09:07 -0600
            Re: .submit(....) problem Denis McMahon <denismfmcmahon@gmail.com> - 2013-06-01 21:11 +0000
              Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 16:50 -0600
                Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 17:10 -0600
                Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 17:27 -0600
                Re: .submit(....) problem Denis McMahon <denismfmcmahon@gmail.com> - 2013-06-02 01:49 +0000
            Re: .submit(....) problem JJ <duh@nah.meh> - 2013-06-02 09:12 +0700
              Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 22:47 -0600
      Re: .submit(....) problem "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-06-01 12:02 +0200
        Re: .submit(....) problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-01 08:45 -0600

csiph-web