I can understand that authorization takes time, however I don't think you've really given the ideas I put forth a fair shake. Particularly when you say:
Then you'd have to make additional AJAX calls to update all the other bits that come with the entire site view (cb, messages, xp). So now you've split one request, with one overhead, into several requests, each adding their own overhead. Now factor in that you can vote for several nodes in a single request without AJAX, but you have to make a new request for each vote with AJAX and you've multiplied the server load many times over yet again.
With respect, there is no reason you'd "have" to do things that way. That would be a very poor implementation. Obviously if you are going to send several AJAX requests for something that currently takes one request, you face diminishing returns. However, in my write-up, I
specifically said that the voting AJAX could work just like the current interface, overriding the "Vote" button itself. This means that we have merely replaced a full page load (on submitting the vote) with a single AJAX request (on hitting the "vote" button).
The entire point of the post was to identify situations which currently require a full page load and replacing those common activities with a simplified (single) AJAX request instead. This would not require increasing the number of trips to the server, but merely doing some of those trips via AJAX rather than reloading the page.
I can accept that such a replacement would provide little benefit if the work done for an AJAX request is almost the same as it is for a page load. However whether that is indeed the case is a question for the
pmdevs.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.