An interesting use case is microsites.
How can I have a set of templates for one domain and another set templates for
another. It seems like that should be included in the request processing
design.
Taking the domain name into account in the request processing may facilate
different content roots and microsites
Eric
Sent via BlackBerry by AT&T
-----Original Message-----
From: "Bertrand Delacretaz (JIRA)" <[EMAIL PROTECTED]>
Date: Fri, 15 Feb 2008 14:24:09
To:sling-dev@incubator.apache.org
Subject: [jira] Commented: (SLING-249) Allow mapping nodes to internet
domains
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569441#action_12569441
]
Bertrand Delacretaz commented on SLING-249:
-------------------------------------------
Can't you use mod_proxy for that, or do you have a use case that wouldn't be
covered by mod_proxy?
> Allow mapping nodes to internet domains
> ---------------------------------------
>
> Key: SLING-249
> URL: https://issues.apache.org/jira/browse/SLING-249
> Project: Sling
> Issue Type: New Feature
> Reporter: Vidar S. Ramdal
>
> 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.
