I can't say I care too much where the wiki lives, but I think it's
worthwhile to wonder what exactly we need/expect to publish on an
official ASF site and what can continue to be done on rollerweblogger.org.
When I take other ASF projects as an example, like the tomcat project
page ...
http://tomcat.apache.org/
it appears to me that they probably accomplish everything on that site
using plain old static html. i don't see any reason why the Roller
project page shouldn't follow that same basic convention and stick with
static content to server up the official ASF project page for Roller.
We don't need an installation of Roller to server up downloads, docs,
FAQ, and other info about how to contribute. it seems like it would be
more of a PITA to try and move stuff from rollerweblogger.org over to
the ASF and we probably wouldn't see any benefits.
it seems better to me if we just leave rollerweblogger.org alone and use
it as the Roller project blog site as it has been for a long time now.
the ASF Roller project page will be standard and can link off to
rollerweblogger.org for the couple things that need to be hosted
elsewhere, like the Roller installation and possibly the wiki.
if it turns out we really, really want the wiki to be on the ASF servers
then i suggest we just pick one of the already supported ASF wikis and
use that. i don't think we should mess with trying to put up a new
Roller installation on ASF hardware, i don't see the benefit. we are
already eating our own dog food on a lot of sites, they just aren't
under apache.org, so what.
-- Allen
Noel J. Bergman wrote:
Dave Johnson wrote:
Noel J. Bergman <[EMAIL PROTECTED]> wrote:
can someone comment on the ability for the Roller + JSPWiki pages
to be cached, which is a key performance and resource utilization
consideration?
The integration between Roller and JSPWiki is lightweight and so you
really have to consider them as separate applications.
Roller has a highly configurable caching system and you can even
plugin external caches like memcached if you want to, but I bet
the out-of-the-box caching would work just fine. Roller is proven
at high-traffic sites like blogs.sun.com, JRoller and IBM devWorks
I suspect that the answer is yes, but is Roller compatible with mod_cache
and other front-end caches?
so I don't think it's performance is going to be an issue on the
little Roller project site.
Wasn't overly worried about it. As you may recall, I suggested at ApacheCon
US 2005 that Roller look into a zone within which to host the code.
JSPWiki uses OSCache for caching. I'm not sure it's been proven at
high-traffic sites. Maybe Janne can comment on that?
Same question as above. Is JSPWiki compatible with having mod_cache sitting
in front of it? MoinMoin was not --- it did things that are termed
cache-busting --- but we fixed it.
--- Noel
