Route using database information

[eluser]WanWizard[/eluser]
I don't intend to make any changes to the core code, that would potentially mean complex merge operations when CI gets updated. I'd like to stay away from that.

I quite like the idea of generating a new config/route.php after an update of the content tree, although I have to see how that works out, with hundreds of one-to-one mappings in $route (and it requires the webserver user to have write access to a file in the docroot, which is not really best practice as well).

I'm not to troubled with two database connections, I tend to use persistent connections anyway. I was sort of hoping that I could utilize some of the CI power, instead of coding everything. That means lots of code, and/or lose database portability (because I can't use CI's abstraction layer).

Taking that into account, probably the best option is to route all requests through my own front controller. That will have access to all CI classes, which makes the database part a lot easier, but it means I have to duplicate the code that loads the final controller and calls the appropriate method, from codeigniter.php.

hmmm... decisions, decisions...