On 7/18/01 5:23 PM, "Kurt Schrader" <[EMAIL PROTECTED]> wrote:
>
> On Wednesday, July 18, 2001, at 03:33 PM, Jason van Zyl wrote:
>
>>
>> <cut>
>>
>> I would like to see all projects use the TDK than we have a single
>> well defined development model. When the model is improved all turbine
>> projects benefit. The TDK should allow the CVS setup to be simple for
>> a project and allow developers to work directly with what's in cvs and
>> not have to copy anything like templates in order to test. The TDK
>> will manage the complexity. The TDK will provide migration strategies,
>> a testing framework for apps, a benchmarking suite and deployment
>> strategies. With a TDK like this there will be no benefit for a single
>> project to try and duplicate anything the TDK does.
>>
>
> So the TDK will become an aggregation of all of the old parts of Turbine
> that are being broken apart currently (turbine, torque, services, etc)
> and then the example app will be built on top of that?
No different than it is now. The TDK right now is an aggregation of
tools to allow easy development with Turbine. The sample app can
come in two forms: the current form and an external bundle to show
how a project can be stored in CVS and still use the capability of
the TDK. There will also be other Turbine projects that can also
be used as examples. Hopefully they will all be the same so there
will be many examples.
> I think that if this is the case and applications such as Tambora,
> Jetspeed, and Scarab are going to move to being built on top of the TDK
> and the services provided by it, instead of building upon straight
> Turbine, then the example app should be broken out into it's own
> repository when the time is right and we actually have two questions
> here.
I would say build with the TDK not built on top of the TDK. As said
previously the example can be bundled separately as well, but I think
it's current form is good for getting started. We could even have an
ant target to convert a project that was started in the conventional
manner to an external project. Just a matter of copying a bunch of files
to a target directory that matches the spec'd structure.
> 1. What generic set of services should be provided by the TDK for apps
> to build upon?
This should be configurable I think. The build system for the services
should allow them all to be built separately into JARs, and the service
broker made to pull in individual JARs and activate the service within. The
sample app could include all the JARs but when deploying a selection can be
made so that the app can be as small as possible while providing the desired
functionality.
> 2. What do we want to do to the example app to make it more relevant
> for people evaluating Turbine as a possible solution and what should
> added to show off more of Turbine's features to these people?
The sample app should be a demonstration of everything turbine can do
because it should become the live system test bed. A series of
cactus/httpunit tests will be run against the sample app on a regular
basis. Hopefully daily, Zenplex is going to put a fast box together
on a well connected line where results will be made available for
perusal. I also have a new box that will mirror this test machine, but
I haven't even had time to take it out of the box.
> Am I correct in my understanding here?
Not entirely, the TDK will behave as it does now, but also provide
a mechanism for development from a standard CVS repository. The TDK
will provide all that is necessary for development and allow easy
selection of functionality so if you only need a couple of services
than you can package just those two services.
>
> ----------------------------------
> Kurt Schrader
> [EMAIL PROTECTED]
> http://www.kurtschrader.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
