I realize that since I'm not a developer I don't have much of a voice here
but, if I understand the flurry of communication today, as a user I'd
_definitely_ be a fan of releasing 2.3 as it seems to stand now -- not
(overly) fulcrum-ized or avalon-ized or anything-else-ized and fairly
straightforward to setup with existing applications. The current 2.3 code
fixes issues that have really been a thorn in what seems like (from mailing
list volume) a great many users' sides. It would make sense to me to plug
these particular holes in the dyke before rushing off to build exciting new
walls.
Your users will thank you profusely as the vast majority of them have zero
interest in how cool avalon/fulcrum/some-other-container-of-the-week
can/will be (although the conversation has brought to light some exciting
developments for the avalon-ized turbine) and just want their applications
to work. As a user who's contentedly used avalon in the past and moved to
turbine's services framework I think it'd be a great thing (configuration
problems not withstanding) ... after 2.3 -- one last monolithic release.
Please!!
*returns to the peanut gallery*
-j
"Henning P.
Schmiedehausen" To:
[EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
> Subject: Re: [VOTE] Fulcrum
deprecation
Sent by:
[EMAIL PROTECTED]
ermeta.de
01/13/2003 05:18
PM
Please respond to
hps
"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>Fulcrum was never released. There has also been some work backporting
>code from Fulcrum into the turbine-2 code base. I would anticipate that
>there will be even more work to get the remaining services backported as
>well.
>The current plan is NOT to use Fulcrum for version 2.3. We do want to
>be able to Avalon components. Considering that we want this ability in
>2.3 and we don't currently use Fulcrum, I see no reason not to modify
>Fulcrum to use Avalon.
Hi,
actually, I don't plan on backporting any more stuff than the
CryptoService (which was done by something resembling "find . -name
\*.java | xargs sed -e 's/fulcrum/turbine.services/g'") and the
extended DB Security Service which is painstakingly difficult, took
most of my Saturday and Sunday and still is not in there.
I do this, because there is demand from Users. To me, 2.3 is the last
release with coupled services. Actually, in our internal repository,
we're using a stripped down turbine-2 called turbine-light with
fulcrum since quite a while. I can send you the sources if you want
to.
Basically, pre-Avalonization, the Fulcrum and Turbine-2 code was
identical except that you had to substitute "turbine.services" with
"fulcrum". That made code moving back and forth easy. That's why at
least I want to delay the complete assimi^Wavaloniziation until post
Turbine-2.3. Which at least in my personal road map is planned End
January.
Regards
Henning
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
