It's a bit of an improvement upon the old DOM-model, isn't it?
So especially, for the queue-view (and history), wouldn't it be an idea to consider using jQuery instead of the "refresh the entire page"-doctrine?
jQuery
Re: jQuery
That type of refreshing is not limited to jQuery, it also a standard way of making ajax calls.
Replacing the entire page has its benefits (AHAH) over JSON or XML based ajax.
- Much less CPU intensive.
- Easier to develop.
- Easier to maintain.
Plush uses jQuery, however it fetches the full html and replaces the queue/history with the full html (0.5 will make less of calls, making use of the new advances in the API and doing them only when the whole table needs to be refreshed.)
SMPL uses Mochikit, using both full html requests and replaces (AHAH) and json based ajax for updating the speed box and any areas in the left sidebar.
Default does not use any javascript for refreshing, instead using meta refresh to load the whole page.
Replacing the entire page has its benefits (AHAH) over JSON or XML based ajax.
- Much less CPU intensive.
- Easier to develop.
- Easier to maintain.
Plush uses jQuery, however it fetches the full html and replaces the queue/history with the full html (0.5 will make less of calls, making use of the new advances in the API and doing them only when the whole table needs to be refreshed.)
SMPL uses Mochikit, using both full html requests and replaces (AHAH) and json based ajax for updating the speed box and any areas in the left sidebar.
Default does not use any javascript for refreshing, instead using meta refresh to load the whole page.