Jon Stevens wrote:
>
> on 10/15/2000 11:39 AM, "Travis Low" <[EMAIL PROTECTED]> wrote:
>
> > Thank you, that is very useful information. Now I can schedule a developer to
> > look into moving from
> > Apache+JServ+mod_ssl to Apache+Tomcat+mod_ssl.
>
> I don't see why what I said should affect this decision. Have you been
> sleeping for the last 6 months? :-)
I have three small children. What is this "sleeping" you speak of?
:-)
Anyway, I was fairly sure I could move from JServ to Tomcat without
too many problems. That would be a one-time effort. I was also
fairly sure I could make Turbine work with Tomcat, also a one-time
effort. But moving TDK-developed code into Tomcat+Turbine was an
unknown quantity, and that would definitely NOT be a one-time effort.
Now that I know a single copy command will do it, I'm happy to have
developers use the TDK instead of raw Turbine.
I know I could have checked into this earlier, but my "things to check
into" list is very large. You know how it is.
> However, this shouldn't stop you at all from using whatever version of
> Turbine that you would like to use with the TDK. All you need to do is take
> your own snapshot of Turbine, build a .jar file and replace the
> turbine-2.0.jar file in the TDK with whatever version of Turbine you want.
The version of Turbine I want to use is the version that comes already
packaged with the TDK. I know I could use other versions, but good QA
practices demand that I treat the TDK as a black box.
This way, should we find a Turbine problem, we would first download
the latest TDK and reproduce the problem there. If the problem goes
away, then we'd upgrade to the newest TDK and do a round of regression
testing. If the problem still exists, or we uncover new problems,
we'd submit patches to the mailing list for inclusion in later
Turbine/TDK versions.
If we use Turbine from CVS, we risk incurring a larger cost in both
testing and development. From what I read on the list, sometimes the
latest CVS doesn't even build properly.
If we maintained our own version of Turbine, it would eventually
become incompatible and we'd miss out on important enhancements and
bugfixes, as well as the opportunity to contribute our own
enhancements and bugfixes.
If I'm laboring under any misconceptions, please feel free to correct
me.
-- Travis Low
<mailto:[EMAIL PROTECTED]>
<http://dawnstar.org/travis>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
