[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649642#action_12649642
]
Bertrand Delacretaz commented on SLING-249:
-------------------------------------------
> We will probably not use query, because the current query implementation is
> optimized at doing
> full text searches...
>...Instead the resource tree is scanned for sling:virtualPath properties and
>caches them internally...
A query like
//element(*, sling:whateverMixinWeChoose)
is certainly more expensive than scanning a few nodes that you know where to
find, but do you really want to scan the *entire* repository at startup? That
won't scale.
As the query would run only on service startup (observation takes over after
that), I don't see a problem with using a query.
> 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.
