David Leangen dijo: > *********************************************************** > > [ ] A. I think that we should show users the "best" way > to get up and running with Cocoon. > [ X ] B. I think that we should show users all the options > possible and let them decide the best approach. > > [ ] C. Yeah, whatever. Either way is good for me. > Peace, man!
Because we cannot have a one size shirt for all people ie: If someone need Cocoon as: 1- a publisher framework + 1 feedback form + 1 host book (or whatever). 2- a webapp framework for a small-medium size company 3- a webapp framework for a medium-large (enterprise) size company .... etc. Then you can make diferents configurations and the best practices are diferent for each one. Some questions are in place before choosing the right tools: What if the user already have implemented or want to use J2EE? What if there is already some work on PHP? Will be the application scalable or not? How easy the scalability will be? Will be deployed on an Application server or just on a Servlet container? ....And we can continue puting question on the list. >From a 1 server bundle all to a full distributed system using J2EE. Then the question is: "What is the best practices at all?" I prefer to see Cocoon as is on the Website: "web glue for your web application development needs" That is Cocoon and every one can use it as he need. Best Regards, Antonio Gallardo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
