Expand my Community achievements bar.

SOLVED

Is there a way to have non matching folders under /etc/map?

Avatar

Level 7

Two questions:

1- Is URL Mapping for hosting multiple websites on multiple domains (http://www.cognifide.com/blogs/cq/multidomain-cq-mappings-and-apache-configuration/) a viable solution for a system that might end up hosing thousands of web sites? This could lead to 4 entries per site under /etc/map and judging by the way the link checker transformer works, I think that might lead to unacceptable response times for dynamic pages as well as first hits to static pages that can be cached by the dispatcher.

2- Is there a way to have non-matching folders under /etc/map?

For example, I want to have a folder structure like this:

    /etc
       /map
          /a1
            /b2
              /c3
                /http
                    ...
          /a2
            /b3
              /c4
                /http
                    ...

But I don't want `/a1/b2/c3` or `/a2/b3/c4` to be components of the generated pattern in which requests are matched against. Alternatively, the following structure would work as well:

    /etc
       /map
          /http
              /a1
                /b2
                  /c3              
                    ...
          /http
              /a2
                /b3
                  /c4
                    ...

In which, again, `/a1/b3/c3` and `/a2/b3/c3` won't be included in the URL mapping patterns.

I am using CQ 5.6 with the bundled version of Sling.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi,

before you try to come up with something different: Have you already built a testcase which creates thousands of such entries and measured the performance impact on link rewriting? Because the whole mapping information are held in memory and updated on change of the nodes below /etc/map.

cheers,

Jörg

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

Hi,

before you try to come up with something different: Have you already built a testcase which creates thousands of such entries and measured the performance impact on link rewriting? Because the whole mapping information are held in memory and updated on change of the nodes below /etc/map.

cheers,

Jörg