http://qs321.pair.com?node_id=516386


in reply to Re: AJAX-based Perlmonks.com?
in thread AJAX-based Perlmonks.com?

I'd love to have 'asynchronous' node voting. It's annoying to have to click each node you want to vote on, scroll to the bottom, then click 'Vote' (sometimes I forget to actually submit the form when reading a long thread)

I read long threads entirely different. When I feel like voting on a node, I check the appropriate radio button. Then I go to the next node. When I'm done with the thread, I hit the vote button. Now my -maybe- 10 votes will be handled at once, thus less bandwidth than 10 asynchronous request on the server.

--
b10m

All code is usually tested, but rarely trusted.

Replies are listed 'Best First'.
Re^2: AJAX-based Perlmonks.com?
by gregor42 (Parson) on Dec 15, 2005 at 16:35 UTC
    10 votes will be handled at once, thus less bandwidth than 10 asynchronous request on the server.

    Just to pick nits - you'd be reducing the number of transactions, but not necessarily the bandwidth requirements. You still are reloading all of the content for those 10 nodes every time you submit votes. Asynchronous requests would only send the vote information & (user id, node id, vote type) and receive confirmation information (current reputation tally for node).

    Adding up all that data you still have less bandwith required in total.

    AJAX excels in reducing bandwidth when you do things like this - decoupling functionality from content and only sending page updates rather than the entire page. Yes, you might increase the number of transactions, but you are making their function more granular and thus simpler to process with less overall generated network traffic.



    Wait! This isn't a Parachute, this is a Backpack!
Re^2: AJAX-based Perlmonks.com?
by andyford (Curate) on Aug 10, 2006 at 15:29 UTC
    I do this too, but I often lose track of how many times I've voted. The instant AJAX feedback on voting would help in that regard.