Hi Subscribers, Ok, I want to support Matt's opinion as a developer that sometimes had troubles to move my projects forward.
As long as there was NO PROGRESS on porting AxKit to Apache 2 I definetely agree that AxKit really could work as Perl XML publishing framework that will not linked with Apache server and mod_perl. There are known problems of XML::LibXML under mod_perl, various situation of memory cleanup problems, etc etc etc. It's not bad idea to run AxKit apps independently and later think about linking working app to Apache or another software. Matt compared it to Rails (Ruby on Rails) that, as well is big framework with it's own ways to run robust things: - slowest way to work as cgi - more powerful and debug-featured own webserver - way to work as mod_ruby handler - fast-cgi connector to use in real-world servers with frontends If noone could port current AxKit to Apache2 and make it reliable, I agree with Matt that it could be separated from Apache as long as there are ways to make it fast and usable for big apps. Alex. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
