[
https://issues.apache.org/jira/browse/SLING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763058#action_12763058
]
Alexander Klimetschek commented on SLING-1137:
----------------------------------------------
I would refrain from building in an automatic mechanism that creates hash-based
paths because they are bad ;-) It's better to find a proper semantic structure,
and the most general structure are dates (eg. 2009/10/07/*) as most content has
a date.
I wonder if we could make the NodeNameGenerator in the SlingPostServlet a
service and thus extensible. For example, a new node name generator for this
would listen to a new parameter, eg. :hierarchicalNaming = date, and create (or
reuse) the appropriate date structure for any new node that has to be
generated. (The date may be extracted or given in another parameter).
Thinking further: as you'd probably want multiple node name generators active
at the same time, there should be a proper selection mechanism. Maybe through a
param (:nameGenerator)!?
> 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.
