On Wed, 12 Nov 2003 10:19:57 +0100, Remy Maucherat wrote:
>Edison Too wrote:
>>Hi,
>>
>>I agree with Stefano's observation that there is a need for a good content
>>repository. I've looked into Slide's code before and I can't help but wonder
>>if it is a good idea for Slide to be implemented using Avalon.
>>
>>
<Snip/>
>>Thoughts?
>
>If I was still involved in this project, the answer would be: of course not.
>Avalon provides a set of utility components which all seem inferior to what is
>available in the commons without any strings attached, and as a result, I've
>been very careful to avoid using it. As for deployment of "blocks" or
>"services" (if you really need it in this case), a JMX based model (using
>commons-modeler 1.1, of course) is immensely more flexible, introduces almost
>zero coupling in the application, and is standards based.
>
>Of course, Slide committers are free to decide to do whatever they want :)
>
>R�my

Hi,

I agree there exist many commons component that mirrors those excalibur components, I 
was at first bewildered at their similarity. However, who knows, Avalon may move 
towards using Commons packages as well. In fact, IIUC packaging Slide's functionality 
in Avalon's Framework interface does not mandate using of Avalon's component. The 
commons packages can still be used.

After thinking it through, I realise that as a WebDAV project, Slide is working very 
well and since WebDAV extends the HTTP protocol, servlet is the smart way to go. In 
other words, Slide does not benefit much from a move to Avalon.

However I'm thinking of the amount of work already put into the core of Slide. Making 
it support Avalon potentially opens up the value hidden in the project. They could be 
useful components outside the context of a WebDAV server. I'm thinking of developers 
who may not be interested in Slide as a CMS but may be interested in using the 
Token-based access mechanism, or caching  mechanism etc. I.e. the Avalon/Cocoon 
community will probably benefit from such a move.

Putting it simply, moving the codebase to Avalon may interest more developers to 
contribute, resulting in more ideas, better testing etc. I guess that is the 
fabled/infamous project cross-pollination. Of course the surface, Slide does not gain 
much, while Avalon/Cocoon gains more.

Cheers,
Edison


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

Reply via email to