On 23 Sep 2006, at 05:27, Lars Skjærlund wrote:
You should have a look at plugins/typeless_uri. Typeless URIs are a
Good
Thing(tm), and they solve your DirectoryIndex problem as well.
Well, it appears that my problem cannot be solved - you've added an
error message now stating that I cannot do what I want, and
unfortunately typeless_uri doesn't solve my problem as well.
Nothing "cannot be solved" - it's just software, and it seems you've
uncovered a bug in uri_to_file that needs fixed anyway.
So a few questions remain:
* Are the plugins included with AxKit2 meant as examples only to be
modified by the end user, or are they intended as end-user code? If I
modify a plugin, won't the modifications be overwritten by later
updates?
It's a bit of both. I suggest if you're modifying then first copy
somewhere else and set PluginDir to the new path, or rename the plugin
- the names don't mean anything.
* I've now started writing my own modules that replace the default
plugins. Unfortunately, I cannot find a way to let my plugins coexist
with the default plugins. Is this a good thing?
I don't understand why not. Rename or set PluginDir to a new path. Hmm,
thinking about it there may be another bug there if you have two
different plugins called uri_to_file because the compiler doesn't add
the PluginDir to the generated name. That's a bug but an easy one to
fix.
* Or would I be better of choosing another server? I surely miss the
flexibility of AxKit1 I'm sorry to say.
You're being a big help in finding the areas of weakness of AxKit2, but
you have to weigh that against the fact that you're not playing -
you're trying to build something real. Only you can answer that
question. Ultimately I think AxKit2 will be an easier deployment for
your needs, but maybe you didn't have any issues with mod_perl that
way.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
