Well said! I don't mind volunteering myself to draft a Wiki during my spare time.
However, as I mentioned before, I think that we need some type of consensus on these issues... even if that means agreeing to disagree. So, first reach consensus and I'll sum in all up in a Wiki with pleasure. :-) Dave > -----Original Message----- > From: Derek Hohls [mailto:[EMAIL PROTECTED] > Sent: May 3, 2004 21:31 > To: [EMAIL PROTECTED] > Subject: Business Logic in Cocoon Applications? > > > There have been a number of threads on the mailing list (April 2004) on > the issue of "where to locate the Business Logic"; with Cocoon Flow, for > example, coming under criticism (and defence) for its potential to act > (correctly or incorrectly?!) in this respect. > > It would be very helpful to set up a "good practice guide" for Cocoon > users that identifies (a) what types of logic one encounters [what do we > actually mean by 'Business Logic', and there are any other types??] and > (b) how and where to go about implementing these in the various layers. > As always, clear examples would help new users. > > I do not think it matters if the application is small or large, simple > or complex, the principles and approaches need to be consistent so that > one can transition from between projects knowing that the "same things > will be in the same places". > > Any takers to draft a Wiki Page on this topic? > > Thanks > Derek > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > MailScanner thanks transtec Computers for their support. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
