I haven't gone through it completely to work out all the pitfalls, but the URL information is stored in the cms_node table. You should be able to pull the node information based on that...
However, this field is nullable within the database, because the node is reserved when you begin to create your content, not while the content is saving. So, you'd have to modify the router to take into account two scenarios...use the URL when it's available, and the nodeid when it's not.
There are probably other gotchas, but that's the one that initially jumps out at me.
|