Hi Bertrand, > Same-name siblings are a bad idea in general [1], mostly because their > paths are unstable.
In our application we allow people to reorder the information within the tree. And they do frequently. So our paths are unstable in general. We break with Davids model here and fallback to uuid lookup behaviour. So paths in our case are more for information then for identification. > So IMHO we should leave it as is in Sling and have people create their > own move operations if they really want to use same-name siblings. I am fine with implementing my own move operation. Anyway would it be worthwile to extend the move operation? Is it so uncommon, that people want to move a resource as child to another resource where one with the same name exists? Theoretically that is always possible and if I don't want to implement my error handling on the clientside, I always need to create a custom move operation to deal with that situation. If sns shouldn't be used it would be quite handy to specify that the name generator should be used to generate a new name for the resource automatically. Regards, Markus
