From what I understand this approach is wasting resources.

:) Not that many extra ones that aren't wasted already

Its very much like hitting talk or refresh in chatterbox

It is a common viewing pattern to view a node, vote on it, then scroll down, to see a reply you like, vote on it, and so on

Also common to open a node in a new tab and do the same

So resource wasting? Not really

But it doesn't have to do that, code could pick a different node that returns less byes, like 162 bytes

Or it could simply "cue" votes and cast them every 30 seconds at a cost of under 500 bytes

as I already said

as I already agreed :p

> Its ...

*It's

> ... very much like hitting talk or refresh in chatterbox

The difference here is that CB has not only already plenty of lean alternatives (like sidebar) but also "tickers" which could be called with JS support in the CB nodelet (hence AJAX )

OTOH no voting ticker yet.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}

The difference here is that CB has not only already plenty of lean alternatives (like sidebar) but also "tickers" which could be called with JS support in the CB nodelet (hence AJAX )

Rendered by the XP XML Ticker is close enough

Is the vote count really important to the voter? As long as they cast their ++ or -- ... the reputation can wait for page reload