> Cocoon IS supposed to be used on large, 100% dynamic sites. The best part
> is that all the content, frontend and business logic is separeted so that
> your team can work much more easily. XML based content(written by your
> content managers) is converted to the requested document type on the fly
> (be it HTML or PDF or WML) after being transformed through the appropriate
> XSL stylesheet(written by your designers) interpersed with your business
> logic(written by your programmers - I am still not clear on this part).
>
> But the problem is in the processing capability. These sort of conversions
> can't be done in real time with existing infrastructure. Most of the
> cocoon work being done now is to minimise this processing time, but they
> still admit that it can't be done in real time in commonly available
> infrastructure.
>
> But it is a great concept. And worth keeping track of. This is definitely
> the future in which web content management would progress.
Yeah i read all these stuff abt cocoon. to me it seems that right now it is
well suited for sites which have a large amount of static information that
keeps on changing.. but what i wan't to know is that can cocoon be used to
operate something like say my.yahoo.com this kind of a site needs a lot of
processing on the server..
Bye,
/\ |\/| |3 /\ r
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/linux-delhi/
