"Rodrigo Reyes" <[EMAIL PROTECTED]> writes:
[...]
> Is this the current state of Turbine? I don't think so. We still have
>strong dependencies to specific tools (being Torque and Velocity the most
>obvious ones). It is like Microsoft telling me that it is impossible to
>create a good Operating System without having Internet Explorer embeded.
Well, fact is, in these days you "can't create a good Operating System
without having a Browser embedded". :-)
First and most important move for Turbine would be towards a component
based architecture where we interact between the parts by well known
and defined interfaces. So we won't have any dependencies to a
particular project or tool.
The actual tool access would then happen by (tool-specific) adapters
and/or interface classes.
Basically, this is what we called "avalonization" for post-2.3.
The fact that our "Internet Explorer" ATM is called Velocity (actually
it is more called Torque, because the Scheduler and Security Service
heavily depend on Torque up to the point that Criteria is part of the
method signatures of the Security Service), doesn't mean that it is
impossible to decouple. It just needs work. And unless anyone is
willing to do the work, you will find out that most of the current
developers mainly work to "scratch their itch".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
