> Is there something that you are trying to accomplish that it currently
> doesn't do? If so, then it is probably better to provide that
> functionality
> within Turbine.java itself so that other people can take
> advantage of it.
Ok, for one thing, I would like to put configuration information
in a separate .properties file, and not have to touch Turbine's.
Also, I guess it could become important at some point to show
a "corporate" face by providing a corporate servlet as the entry
point to the app architecture... We would still be telling our
customers we use Turbine, and we would still give them the full
source code for Turbine, of course, but they might feel more
comfortable thinking they are using a "company-supported" servlet
as the basis for their app (not that this means much in reality,
but I've seen corporate minds working this way...)
> -jon
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
