Punky Tse wrote:
>
> > My dream KMS architecture is something like this:
> >
> > [frontend] - [CMS] - [backend]
> > |
> > [store]
> >
> > where cocoon powers both 'frontend' and 'backend', CMS wraps around an
> > native XML database and provides versioning, access control, transparent
> > query filtering and all the required things. 'store' is implemented with
> > a mix of 'native XML databases' and 'relational databases' (depending on
> > the needs, still I haven't designed the whole concept, but I'm not sure
> > that a native XML DB is capable of doing everything without serious
> > performance degradation).
> >
> > What do you think?
>
> So what is the role of Cocoon at backend? Is it used to handle all sort of
> generation and transformation? Obviously, frontend is used for
> presentation.
I picture a web-based frontend as well as a web-based backend.
Cocoon powers the backend just like it powers the frondend: serving the
pages.
Sure, you might not need the 'full' cocoon potentials on the back end
(but to provide previews or completely WYSIWYG inline-editing, you do!)
but I see the backend as an-editing oriented web(dav?) application on
top of Cocoon.
(yes, it's piece of cacke to add WebDAV functionality to Cocoon
directly, it's just a bunch of new HTTP actions and some XML content,
not a big deal for our machinery)
Also, consider things like having editors down in Afganistan feeding
their news via Palm connected to satellite cell-phones (UTMS anyone?),
having their directors approuve the news while they are on an airplane,
with the ability to annotate things directly on the page and without
requiring any specific software to be installed on either client.
See the need for cocoon on the backend? :)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
