21
edits
AniDB:AJAX development: Difference between revisions
→XSLT
No edit summary |
(→XSLT) |
||
| Line 81: | Line 81: | ||
==== XSLT ==== | ==== XSLT ==== | ||
* Ups: Server throws out the xml, which is also used for ajax. so theoretically, when we have ajax, xslt comes for free. the style sheet is static. meaning can be cached etc. The xml file is also largely static (no dynamism due to user settings. It only needs to change when anime data actually changes.) Also allows splitting of data into domain. e.g. the same basic anime xml used by all. files and member only data can be sent in another separate xml to be merged on client's end. XSLT is available on almost all modern browsers. | * Ups: Server throws out the xml (no html at all), which is also used for ajax. so theoretically, when we have ajax, xslt comes for free. the style sheet is static. meaning can be cached etc. The xml file is also largely static (no dynamism due to user settings. It only needs to change when anime data actually changes.) Also allows splitting of data into domain. e.g. the same basic anime xml used by all. files and member only data can be sent in another separate xml to be merged on client's end. XSLT is available on almost all modern browsers. | ||
* Downs: There are still some browsers that don't do xslt. Also, a little hard to debug (that's a developer's problem), coz the source cannot be seen (if you look at src of a xslt generated html page, you won't see the html. you'll see the xml) | * Downs: There are still some browsers that don't do xslt. Also, a little hard to debug (that's a developer's problem), coz the source cannot be seen (if you look at src of a xslt generated html page, you won't see the html. you'll see the xml) | ||