Database driven routes in CodeIgniter

[eluser]neillyons.co[/eluser]
@clooner Not sure if you arrived at this forum topic directly or through my more recent post. There I talk about including a cache file in the routes.php file similar to what your describing. Although the cache file is not created when you access a certain controller but whenever an insert/update/delete operation is performed on the route model.

With your solution I think there might be an issue with lag time. For example, say I have just created an article on my website. It has CodeIgniter's default route of articles/get/1 and an alias of that route like so articles/my-example-article.

I'm assuming your updating your cache file on a cron once a day. So the time between the article being created and the cron being run that route (articles/my-example-article) will produce a 404 error.

Does that make sense?