[
https://issues.apache.org/jira/browse/SLING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763077#action_12763077
]
Ian Boston commented on SLING-1137:
-----------------------------------
I agree with the plugin approach since there are plenty of situations where
there is no semantic structure that does not generate scalability and
concurrency issues (until JCR-642 has been fixed), for those situations you
have no option but to use something that generates a flat distribution of node
paths throughout the chosen taxonomy.
It might also be helpful to distinguish between JCR path and URL path, since
they IMHO don't have to be the same and it would be completely wrong to expose
an JCR path structured for scalability and concurrency to the user.
eg
http://myresearch.cam.ac.uk/~ieb
where ieb is one of 25K users.
putting that in jcr as /users/_ieb wont work, but giving urls out like
http://myresearch.cam.ac.uk/i/e/~ieb
will just be embarrassing (afs eg
https://www.sit.auckland.ac.nz/Mapping_a_network_drive_to_an_AFS_path_%28Windows%29)
> Support hierarchical child node creation from SlingPostServlet
> --------------------------------------------------------------
>
> Key: SLING-1137
> URL: https://issues.apache.org/jira/browse/SLING-1137
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Mark Baker
> Priority: Minor
>
> The default node creation functionality on "/" terminated paths via the
> SlingPostServlet doesn't scale very well as it only supports creation of
> nodes immediately under the targeted path. So, for example, when using this
> via a CQ form to capture form responses in the repository, a site can
> potentially have thousands of child nodes, leading to well known performance
> problems.
> I think it would be useful to offer an option for the servlet to save a
> hierarchy of nodes, perhaps via the common convention of using the first 4
> characters of the would-be node id to create a 2 level hierarchy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
