> 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. > > -- > Stefano Mazzocchi One must still have chaos in oneself to be > able to give birth to a dancing star. > <[EMAIL PROTECTED]> Friedrich Nietzsche > -------------------------------------------------------------------- Punky > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
