[eluser]jedd[/eluser]
Of course.
Earlier on you said you were worried about ROUTE changes, because you would have to hard-code things. This meant that if any new things were added - by a user perhaps - you would have to hard-code NEW routes in to handle them.
I suggest that you invert this problem. Rather than route a bunch of things that you list, you instead route everything that is NOT in a list.
As I say, this is only helpful if you think that in the future, the kinds of changes that will occur are more likely to be things that you want to automatically route by default. I expect that there will always be times when you need to visit your source and make hard-coded changes to the way things work.
Does that make more sense? I think the key here is just reversing or inverting your routing condition - exclude from one set, rather than include from a different set.
