> > IMHO the content structure is a critical part of the system > (at least > > on the technical side), so I would involve a developer with > knowledge > > and experience about the "underlying" repository and > content modeling > > whenever a new URL space is created by some application. Or > teach the > > UI developers about content modeling and provide them with > simple APIs > > to avoid flat or hash-based hierarchies. > > I agree, I have been trying to do that just for the past 18 months. > Sadly the non technical view is that the URL space is *user* space, > which has been the motivation to provide some virtualization between > jcr URI's and http URI's.
IMHO, it's not important if the URL space is UI space or developer space. It's a simple fact that there are use cases where we have thousands of resources under the same node, which are not structurable in a reasonable manner, like users under a node /user/. But it's also a fact, that we need a solution here only because Jackrabbit does not scale very well if the structure is flat. So the real solution to that problem would be so solve https://issues.apache.org/jira/browse/JCR-642. But as you have a look at this issue it doesn't seem to be solved in the next time. That's why I think we should provide such a service in Sling which - there I'm totally agree - is in fact only a workaround. - But a very needed one. best regards mike
