Unfortunetly the order of loading of external resources is the browser's choice, and I know no way of affecting this. Btw, do you think that these blocking causes the stalling of pushing for you? If it is, then it should show the Pushing cancelled error msg sometime. Does it show? If it is the cause of the error, then the introduction of an initial phase should solve this. It creates the requests in an initial state, which they can have notifications, but those won't be propagated to the client, until it sends a keepalive. It should timeout longer then the next keepalives.
sashee On Fri, Sep 25, 2009 at 3:33 PM, Matthew Toseland <t...@amphibian.dyndns.org> wrote: > The Activelink Index has 8 style sheets. In my testing, the XMLHttpRequest's > from the javascript are only sent after the style sheets have been loaded - > which because there are tons of other requests going on, can take some time, > enough in this instance for a timeout. > > AFAICS the easiest way to deal with this is to increase the timeout to 10 > minutes. IMHO this is acceptable as page close notifications will be > propagated anyway unless the browser actually crashes. I have however seen > timeouts in the past with a 10 minute timeout, which are likely caused by > other issues. So I will continue to debug ... > _______________________________________________ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
