Re: [Webmacro-devel] org.webmacro.util.Clock + Logging

[Brian G. <br...@qu...>]

> IMHO, I think that WM shouldn't fire up _any_ threads w/o being asked.

The problem here is that WM is many things to many people.  Some use
it as a servlet-based templating service.  In this context, it is
entirely reasonable for it to use threads (although marking them as
daemon threads would be polite.)

Some people use it strictly for its formatting capabilities -- in this
case, a lighter-weight means of invoking it (no caching, no threads,
etc) makes more sense.

But in the context of something that's going to live in a servlet
engine, a "no threads" rule is kind of silly.  That's almost as
arbitrary as saying "no inner classes."  Individual threads are just
not that expensive.  If it turns out to be more efficient to have a
housekeeping thread or two, there's nothing wrong with that.  

I think the real issue is that WM is lacking any sort of framework for
easily starting only the parts you need.