On 21 Jun 2004, at 16:29, Kip Hampton wrote:
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.
They're a requirement on Windows where AxKit runs single threaded (a http request back on yourself creates a deadlock). They're also a requirement for running under -X.
#2 sounds like it might be a bug.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
