Hi John, On Mon, Apr 6, 2009 at 5:25 PM, John Crawford <[email protected]> wrote: > On Mon, Apr 6, 2009 at 10:16 AM, Pontus Amberg <[email protected]>wrote: >> ... >> [1] https://issues.apache.org/jira/browse/SLING-249
> Ya, thats what I was thinking, using an Apache proxy w/ virtual hosts and > hit a specific context path (domain)... Yes, and that's also good for security/isolation, virtual hosts make it impossible to reach things like the admin area from the outside. > ...was just wondering about > scalability. Most hardware can handle hosting 80 sites with moderate > traffic, but was wondering a bit about the abilities of Sling / JackRabbit... Depends on what you mean by "moderate traffic" of course. I'd suggest that you run some load tests based on expected content, traffic and caching patterns. If you're going to have an httpd server as the front end, you can also take advantage of caching there, by including HTTP cache headers (which might depend on content) in Sling's responses. I wrote a simple load test tool a while ago, that allows you to generate semi-random http traffic based on simple java classes, and gives quick visual feedback of your server's response times. Maybe this would be useful in your case, see http://code.google.com/p/httpstone/ . There are many other good tools for that, of course. > ...I guess that is really my solution and the answer to my question. Just > have > a common set of components / templates (with varied layouts), which is > similar to the CQ design... There's only just so many ways you can rearrange > a site.... Yes that sounds like a good solution, and if you can keep all this into a single workspace with a good virtual host based URL design, that should make things easier. > ...Thanks for the discussion... Thank you, it's always good to hear from people's varied use cases! -Bertrand
