[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649619#action_12649619
]
Felix Meschberger commented on SLING-249:
-----------------------------------------
Caching and cleanup:
Yes, we need a cache we use JCR Observation to manage the cache (that is simply
clear it on changes)
Queries:
We will probably not use query, because the current query implementation is
optimized at doing full text searches, which is not exactly what we would need
to do. Therefore these queries will be expensive. Instead the resource tree is
scanned for sling:virtualPath properties and caches them internally.
Domain Roots:
As explained in [1] the easiest way is to use the use the existing
sling:vanityPath property for all needs and not introduce a new property.
[1] http://markmail.org/message/aa3civ2m4ql3cnkx
> 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.
