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

[Aske Ertmann]

Hello

@Adrian:
I assume we're talking about the node's identifier property as the UUID. And that right, the purpose of it is to remain the same across multiple contexts.

@Robert:
Sorry I didn't mention my thoughts about how to solve it. Anyway I was thinking of using the node identifier for all links to keep it separated from the node paths. At least for all links inserted with a link browser/suggest wizard. We could also support node paths, but not sure if that is necessary. For link suggestions I imagine we still show the node path when selecting the link, but insert the identifier in a actual code (invisible to the user).

Not sure what the advantage of a (cache) table would be? Wouldn't adding a key for the identifier field suffice?

Aske

On 26/03/2013, at 10.36, Adrian Föder wrote:

> Hi,
> 
> Am 25.03.2013 13:27, schrieb Robert Lemke:
>> Which disadvantages can you imagine if we used UUIDs?
> 
> oy... we're talking about the "identifier", no?... I always had the persistence_identifier in mind...
> Well OK, the Node Identifier would be good of course... if nodes are cloned into user's workspaces, exactly that identifier will stay the same, right?
> 
> Greets,
> 
> Adrian
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5