347
edits
AniDB:AJAX development: Difference between revisions
Jump to navigation
Jump to search
m
→AJAX
Fahrenheit (talk | contribs) m (→AJAX) |
Fahrenheit (talk | contribs) m (→AJAX) |
||
| Line 90: | Line 90: | ||
* 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?? | * 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''] | |||
* 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) | * 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) | ||