cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: Vote: to unify, or not to unify - results
Date Tue, 04 May 2004 17:07:53 GMT
I would suggest that if you want to write "best/good practices" that they be
done under "classifications", i.e - what kind of website you have.

I think it would be quite useful to have a guideline for how to write a
simple site (although you could get a lot of that from the sample site), as
well as one for a larger site, and one that uses EJBs. 

I have seen the petstore implemented in many ways to illustrate whatever
technology was being discussed - I believe Sun even has multiple versions of
it.  To be honest, I've never looked at Cocoon's petstore. Mostly, I guess,
because I knew it didn't use EJBs.  However, it would be cool to be able to
go to the Cocoon site, read descriptions about various implementations of
the petstore, and then download the one(s) that sound relevant to the
project being developed.

Just a thought.

Ralph

-----Original Message-----
From: David Leangen [mailto:dleangen@canada.com] 
Sent: Tuesday, May 04, 2004 9:17 AM
To: users@cocoon.apache.org
Subject: RE: Vote: to unify, or not to unify - results


Generally, based on your comments, it appears that a good approach may be to
choose a "currently preferred approach". This recognises that what is often
called "best practices" may change over time. This makes sense to me. So the
CPA method allows for future changes (without loss of face), while still
allowing us to focus on one particular approach for beginners.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message