On Tue, 17 Jul 2001 05:57, Uli Mayring wrote:
> On Mon, 16 Jul 2001, Berin Loritsch wrote:
> > What needs to be done is a Phoenix specific implementation for Cocoon's
> > Environment interfaces--and publish the Service interface and write
> > a descriptor.
> >
> > The hardest part is the Environment integration.
>
> I'm still in the process of getting used to identifying the various
> components of Avalon seperately. For me Phoenix always was an integral
> part of Avalon and I can't see how to use Avalon without it - but Cocoon2
> proves that Phoenix is just one server implementation using the Avalon
> framework. I'll get this straightened out in my head someday :)
;)
> Perhaps it would be useful to take Cocoon apart into several blocks, so
> that various people could select the parts they want and build their own
> XML server. Once I learn more about Avalon, I'll be able to tell if it
> would make sense to get my hands on that.
I guess the thing to do in the case of Cocoon is to analyze which things are
"services" (ie candidate blocks) and which are sub-components of blocks. My
first guess would be that you would have at least two services from Cocoon.
The first service would be the XML processing engine. It basically accepted
definitions of transformers, generators, serializers etc.
The second one would be the sitemap service that compiled and implemented
sitemaps. It would use the XML processing engine to implement it but perform
all the logic itself.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
