Re: Server Load
Ignoring all the other problems porting to Ajax would cause, Ajax only saves on reloading the static content. The only thing that really stays static on RPoL is the logo in the top left, everything else generally changes from page to page. Even if the links in the bars were made uniformed it doesn't solve the problem that the majority of the data that RPoL sends is dynamically rendered, namely the main menu (people can add or remove games at any time, the post count can change, so to can the post date, game title, etc) and the heavily load pages I mentioned before; the game menu, the thread display screen and the compose screen (which, if you pause to consider it, you will realise has the last 5 posts at the bottom of it, ergo a mini thread display).
The majority of bandwidth consumed by RPoL (and major cause of resource usage on the back-end) is the threads. Ajax can offer little benefit here and I think a careful approach to our resource problems needs to be taken, not just blindly implementing the latest web craze.
This message was last edited by admin at 06:21, Tue 22 Apr 2008.