Martin Oldfield wrote:
Thanks for this.
Sorry to be dense, but how is this better than just fetching it with http: ? Is it just efficiency ?
"Better" is a matter for debate...
axkit:// URIs differ from http:// URIs that point back to the current host in that:
1) There is no additional HTTP request to get the data 2) All StyleChoosers, MediaChoosers and other Plugins are skipped.
Given that I use the QueryString StyleChooser quite often to create data URIs with alternate "views" selectable by style name, and that using axkit:// URIs circumvents the Plugin phase (hence, StyleChoosers don't work), I personally find them pretty useless.
Cheers, -kip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
