Hi,
I would like to start a discussion on the feasibility
of turning Turbine services into plugins, or blocks to
to use Avalon terminology.
The basic idea would be to have a directory where service
plugins are picked up when a Turbine application is
started. We would have to deal with dependencies among
services and configuration issues, but I think we could
borrow a lot from Avalon as this concept is already
implemented and working in Avalon.
Avalon has a set of core blocks, and in much the same
way Turbine would have a set of core services that could be
provided as standard fair in the Turbine distribution.
But I think this would provide a great way to add
third party functionality to Turbine in very easy
manner. We could provide a clean set of build tools
for making services which we could use for the core
Turbine services as well.
I think this would also help with the current layout
of the packages. I'm personally not very keen on the
org.apache.turbine.services.X
org.apache.turbine.util.X
layout that has evolved. I think all the code for
service should be together. Utilities for a particular
service, that are required for the service to work, are
really part of the service and I think that code should
the code should be grouped together.
I think this organization would be easier to follow,
as everything pertaining to a service would be together,
and would definitely allow an easier migration to
services as plugins.
I'm sure others have thought about this but I just
wanted to get the ball rolling.
Thoughts?
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
