Definitly..  I actually looked at the list of services, and of the original
list, here is the status:

bsf             Not Done.  Does anyone use this guy?  Could be removed?  Or, I guess I
could convert it...  It doesn't exist in torque though..
cache           Done
crypto  Done
db              Not Done.  Not sure about this guy, he basically is Torque.  And
fugly...
dvsl            Done
factory Done
intake  Not Done.
jsp             Not Done.    Don't we need some sort of code from somewhere?
l10n            Done.
mimetype        Not Done.
naming  Not Done.
pool            Done.  (Except I want to use commons-pool under the covers!)
schedule        Partly Done.  I only added a non persistent scheduler.  I would
prefer to skip the torque one and use Quartz  or jcrontab.  Up for much
discussion.
security        Not Done.  A whole can of worms!
template        Not Done.
upload  Not Done.
util            Not Done.  Although really since it is all parsers, should it be
called parser instead?
velocity        Not Done.
xmlrpc  Done.  Can't test though...   And plexus has a much better/newer one.
xslt            Done.

The "Done" ones all have at least one unit test verifying they work.  As far
as the other ones to do, it seems like mimetype, naming, and upload are
pretty simple.  However, velocity, template, intake, and jsp all seem a
little more complex.  Might leave those for a bit.  Although I know a lot of
people would like to use intake outside of Turbine!  and db and security
seem like they should be tossed and replaced with something much better....

The big thing I don't have is the Facade classes that allow you to access
the services as if they where static..  Not really sure how to go about
that, and I almost think that is a Turbine specific chunk of code.
something that belongs in Turbine (post 2.3!) that manages hooking up to
multiple components so you aren't always loading them by role...   Hide the
avalon stuff away from the users.  Any ideas?

Eric Pugh



> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 20, 2003 11:23 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [FULCRUM] Swap in commons-pool for pool service?
>
>
> "Eric Pugh" <[EMAIL PROTECTED]> writes:
>
> >Any comments?  Would this be good for Turbine 2.3?
>
> Good yes. For 2.3 no. I will keep this bugger now in bug fix / doc fix
> / style fix mode and push it out in the next few days.
>
>       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
>
> "Dominate!! Dominate!! Eat your young and aggregate! I have
> grotty silicon!"
>       -- AOL CD when played backwards  (User Friendly - 200-10-15)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to