AniDB:AJAX development: Difference between revisions

* Ups: Rich web experience.  due to partitioning of xml data, potentially a large portion can be more static and cacheable.  meaning server only have to serve the differences. E.g. the server may serve the same anime and episode info to all people, but may send a per-user xml which contains settings, preferences and mylist stuff.  Lighten server load even further?  potentially allow even more user customization like the skinning system (server tells client which skin file you use, which can be set by you), coz now, you can change the entire layout of the page by setting a different xslt/jst file sets??

[''[[user:fahrenheit|fahrenheit]] - you can change the CSS stylesheet on the profile options'']

[''[[user:sphere|sphere]] - CSS stylesheet can only style the fixed DOM, with xslt/jst, the same xml can genereate totally different DOMs (which can be further style by individual CSS).  But this remains just an option atm, since we're still emulating the original anime and it seems good enough that there seems to be little suggestions for some changes that are so radical that CSS alone is insufficient :)'']

* Downs: requires javascript.  heavier on client end (but better client than server, imo).  Have to be made more robust coz there may be higher chances of computer amateurs messing stuff up on their client end (as compared to server-spoon-fed html)  

[''[[user:fahrenheit|fahrenheit]] - for the first part it can be impractical for large animes, for the second, can happen with server-spoon-fed html, we had some greasemonkey scrips before, you can mess with anything that has a dom tree'']

[''[[user:sphere|sphere]] - for the first, I'll like to think for data of anidb's size, it is still mostly ok as we at most deal with one anime at a time, but this is groundless until we can do some testing'']