[
https://issues.apache.org/jira/browse/SLING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763042#action_12763042
]
Mike Müller commented on SLING-1137:
------------------------------------
I think this would be a really cool feature to work around the performance
issue of jackrabbit if you have many nodes under the same node.
What about a service which can be registered unter a specific path which
addresses this issue very transparent for the client:
1) the service takes care that the subnode under the registered path is saved
in a hierachical tree (eg. a tree based on hashes)
2) the service also acts as a ResourceProvider which returns the searched
resource
For example:
1) You register this new service unter /my/path
2) If you post a new node under /my/path/newnode the service takes care to save
the new node in a non flat structure, for example in a hashed structure under
/my/path/b7/newnode
3) If you get the resource under /my/path/newnode the service
(ResourceProvider) takes care the /my/path/b7/newnode is returned.
WDYT?
> 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.
