On Sun, Feb 12, 2006 at 12:08:06AM +0100, Marc Battyani wrote:
> "Gary King" <[EMAIL PROTECTED]> wrote:

> > Does anyone know why the CLD constantly reloads. It refreshes
> > every 2- seconds or so. This doesn't happen in Safari and so is
> > probably OmniWeb's "fault".

I use Galeon, it did this too.  Until I turned JavaScript off.

> > I'm just curious as to what would cause this.

I go a bit further than that, I want to stop it.

I tend to open web pages and leave them there until I return later,
it's a sort of "parallel browsing" which schedules attention in a
somewhat haphazard way.  Currently I have 129 pages open in nine
windows - I don't claim that this is a good thing, I'm just saying
that's how it is at the moment.

My cablemodem has enough upstream to about 37 such pages phoning home
(every 2 seconds, 700 bytes of HTTP headers).  That's it, maxed out.

I think my remedies are,

 - disable JS for the whole browser

 - filter all incoming JS to remove dojo.io.* and anything similar (in
   this case, appending an iframe with a form).  Privoxy may help.

 - use a browser which blocks async calls, the same way it may block
   cookies, images and popups, and for the same reasons.

Given the privacy considerations of asynchronous web applications, I
tend to prefer disabling Javascript.  Even if this means that some web
sites don't work properly.  I've been a bit lax recently, thanks for
reminding me!


> It's because of my Ajax like style Framework. I maintain a
> bi-directionnal communication with the server which is polled every
> 2 or 3 seconds. Normally this should not be visible for the user.

I see it in "xnetload eth0", it was enough to attract attention and
provoke a running of Ethereal.

> This Framework was mostly intended for complex web applications on high
> speed networks so it's probably not tuned for low speed internet access.

Is it actually needed?  Can you switch it off please?

I'm not a complete Luddite here, I'm writing an Ajax-flavoured web app
at work (no XML, but JSON).  The difference is that at work we control
both ends, and chose Ajax because in this case it's easier to deploy
than Perl/Tk running or displaying on the workstation.  It's a
question of using appropriate technology.


Matthew  #8-)
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners

Reply via email to