[TYPO3-team-core-v5] Multi purpose URL scheme for the Flow world

[Robert Lemke]

Hi all,

On 21.03.2013, at 22:43, Aske Ertmann <aske at moc.net> wrote:

> I like the approach you have, and one of the things I'm weary of is the usage of node paths for links since we use them to create our url's as well. I think we need to use the node identifier instead because otherwise we will end up with links breaking every time we move pages around. But I think both should be possible, although links inserted using the GUI should use the identifier instead. At least I think it will be very difficult to update all the occurrences of/relations to the node path once it changes. Same problem occurs when using TypoScript.

just one thought: what if we used the Node UUID for the links and keep a (cache) table which allows us to quickly find the corresponding node? It's not human friendly, yes, but the advantage would be that a link to content will be quite stable, even if you decide to move the content to another website (provided that Neos knows about this).

Which disadvantages can you imagine if we used UUIDs?

Or a mix of node path and UUID - first the node path is used and if that doesn't work, the node path is updated after finding the node via its UUID.

Cheers,
Robert