Tango.info table sort: Difference between revisions
Created page with 'server side vs jquery user feedback: I think your objective should be to give satisfactory performance to all, not better performance to some. Serverside SQL is good because th...' |
No edit summary |
||
| Line 6: | Line 6: | ||
Another advantage of server side is that in the worst cases - where the page is long as in the Canaro example - the part of the page the user is seeing when he clicks for a sort refreshes much sooner than JS, because JS refresh takes place only when the operation has completed. | Another advantage of server side is that in the worst cases - where the page is long as in the Canaro example - the part of the page the user is seeing when he clicks for a sort refreshes much sooner than JS, because JS refresh takes place only when the operation has completed. | ||
also | |||
pro server | |||
* jquery sort on some table columns is buggy | |||
pro js | |||
* in chrome js much faster | |||
* safes server cpu | |||
Revision as of 2009-09-12T21:43:48
server side vs jquery
user feedback:
I think your objective should be to give satisfactory performance to all, not better performance to some. Serverside SQL is good because the time for a sort is never more than the time for the first page, hence you can be sure that anyone who was satified by the time of the first page will be satisfied by the time of the sorted page.
Another advantage of server side is that in the worst cases - where the page is long as in the Canaro example - the part of the page the user is seeing when he clicks for a sort refreshes much sooner than JS, because JS refresh takes place only when the operation has completed.
also
pro server
- jquery sort on some table columns is buggy
pro js
- in chrome js much faster
- safes server cpu