[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649645#action_12649645
]
Felix Meschberger commented on SLING-249:
-----------------------------------------
> //element(*, sling:whateverMixinWeChoose)
The problem with this is (1) that it seems to be really expensive (ok running
it once, might probably be ok) and (2) might block indefinitely because if at
the same time a huge property is indexed, the index is locked and so are
queries.
We might of course start off with a query and then, as experience may tell,
convert to something else.
The advantage of a query is of course, that it is much simpler to use on our
part and is much more expressive than scanning the repository.
> Allow mapping nodes to internet domains
> ---------------------------------------
>
> Key: SLING-249
> URL: https://issues.apache.org/jira/browse/SLING-249
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.2
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> Sling should support hosting multiple domains, with different JCR roots.
> E.g.:
> http://www.domain1.com could map to /content/domain1.com
> http://www.domain2.com could map to /content/domain2.com
> While developing a website, the fully qualified domain might not be
> available. Ideally, the mapping could be configured in a flexible way. One
> option would be to maintain a set of regular expressions to match against
> URLs. Each regexp would then match to a path in the JCR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
