>>> Justin Wells <[EMAIL PROTECTED]> 27-Jan-00 9:59:56 PM >>>
>> I personally would not suggest using a non-standard tool for a
big
>> rollout project that is going to need continued support -
>Really? You wouldn't use Apache? Or Linux? or PERL? Ever?
You know that's not what I meant.
And anyway those examples are all standards, albeit de facto ones.
>I don't think standards are all that important when you are talking
>about opensource applications.
Not so, it's a lot harder to persuade a client to use an opensource
tool that isn't a standard.
I've had no problem persuading clients that GNUJSP is a better bet
than other JSP engines and I've even managed to persuage some people
that GNU-Paperclips is better than commercial servlet engines (though
I have't been able to get anyone to drop Jserv yet).
I haven't tried getting anyone to adopt your tool or indeed my own
(GNU-Weblook) because I personally feel that it's an area where a
client needs to have access to a lot of experience.
>The relevant question then is what is the size of the userbase,
>since that determines your level of support.
>(ie: the more there are, the more people there will be fixing and
>helping other people, and the more people there will be to step in
>and take over if the initial developers leave.)
This is absolutely correct... but an opensource implementation of JSP
is also easier to support than a.n.other tool because the
understanding of how it is supposed to work is there in the wider
community.
My point about standards was about methods... JSP is one method of
fixing the problem... there are others but JSP is the "standard" way.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
