Reduce load of monitor function

[GoogleCodeExporter]

As the DDOS-like effect of the monitor ajax 5-second timeout caused,
it made me think, that the monitor function server side, is not 
aborted if the client disconnects.

This means that when people vote, or click on other things that 
disconnects the monitor function, the original connection still
lives on the server loading it, until it times out or detect an event.

I suggest to experiment with the amount of time the server function
lingers waiting for a new event, reducing it - maybe to a few seconds.

It all depends on how the site is used. If theres lots of clicking about
and few events, it will save us, but if theres lots of idlers, it will not
save us. 

I am also thinking the overhead of making connections is small compared to
the actual polling, so we could be getting a reduced load.

The best thing would be if the server got - and reacted - to a signal once
the connection was dropped, but thats probably a harder thing to fix.

Original issue reported on code.google.com by Fam.Stae...@gmail.com on 13 Jan 2010 at 9:09

[GoogleCodeExporter]

Original comment by FishGuy8765@gmail.com on 24 Jan 2010 at 2:16

• Changed state: Started

[GoogleCodeExporter]

Well underway. Still got a few features missing

Original comment by TheTerra...@gmail.com on 16 Aug 2010 at 6:59

[GoogleCodeExporter]

Original comment by TheTerra...@gmail.com on 29 Aug 2010 at 2:48

• Changed state: Fixed