On Saturday, 23. September 2006 11:27, Lars Skjærlund wrote: > * 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?
I think of the default plugins as a decent base to get going fast, but not as the one and only way to go. As Matt already said, just rename your modified file and use it. > * 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? There is no need, IMHO. The plugin architecture is central to AxKit2 exactly /because/ you are allowed to use your own code for any part of the request. Throw out uri_to_file if you want to do it in a completely different way. > * Or would I be better of choosing another server? I surely miss the > flexibility of AxKit1 I'm sorry to say. What part are you missing? AxKit2 is way more flexible since it is so much easier to use custom components for almost all aspects. Keep in mind that AxKit2 is still young. It already works great, but I bet there are tons of little features that are still waiting to be implemented. Don't hesitate to ask us for features, perhaps someone is already working on it or wants to work on it soon. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
