El 21/10/10 13:38, PChot escribió:
I belive classical mod-rewrite in meaning of htaccess i think is not
good for performance. I beleve more to some client GUI that client
themself can modify redirection in cherokee.
I don't think that's the correct answer for a hosting service.
I can do that for my own server o apps, go to a 'redirection panel' on
Cherokee and set up the redirection I need, but think about giving
hosting service to dozens of clients that need to install and remove
opensource apps that are designed to run "as is" with apache and
mod_rewrite. Then tell them they have to learn a new way to redirect and
rewrite urls, and have to read their .htaccess files for all their apps
and remake them.
Now think you are a hosting provider and have, hundreds, thousands, or
hundred of thousands client.
Nobody says that the Cherokee redirector is no good, but I, that I have
been a hosting provider, know this problem. Your clients just want to
put their software and run it, they don't want to learn a redirect
framework just for starting a forum, a blog, a cms or whatever.
mod_rewite compatibility is something that we've been talking about on
the Cherokee Summit. This one of the main barriers for migration from
Apache as almost every opensource webapp available around needs
mod_rewrite for one thing or another, most usually for pretty urls or
content management. Everybody expects a LAMP stack down in her hosting.
Back in the days I did hosting, a plugin like this would allowed me to
be totally Cherokee, and not only partially...
I think is a great idea...
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
