Jan, it was a looong time ago ;-), but the we (the developers) only had 100 days... If you include all the other people (like project manager, technical coordinator,... who actually didn't contribute to the architecture and the implementation of the site - all they did was talking and working on our nerves) then we had almost 200 days.
Sven On 11 Dec 2001 at 23:38, Jan Uyttenhove wrote: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: dinsdag 11 december 2001 14:40 > > To: [EMAIL PROTECTED] > > Subject: RE: [RT] Managing Flow and Resources > > > > > > > > > > > -----Original Message----- > > > From: Tom Klaasen (TeleRelay) [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, December 11, 2001 10:08 AM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [RT] Managing Flow and Resources > > > > > > > > > > > > > > > > [big fat snip] > > > > > However, XML allows you to enforce some limitations on the users. Java > > > does not. As you can already see in the example above IMHO, > > > it gets very > > > difficult to cling to and enforce the SOC principle. The > > > shopping-cart() > > > function seems to be flow control, but the change-address() is already > > > business logic IMO. > > > > > > Of course, the very intelligent programmers who are > > > developing this from > > > the start, will be able to enforce the SOC for themselves, > > > but newcomers > > > who learn by trial-and-error (as we all do) will have serious > > > difficulties to grasp it, even if they want to. > > > > Very right indeed. I'm currently working on a cocoon-based > > project where the > > original developers also didn't realize the importance of separating > > publishing, flow and business logic. For example, the business logic is > > partly in the publishing pipeline, which has as a consequence that certain > > flow decession can only be made in an xsl that generates html to redirect to > > another page (ugly!) and more such stuff. Also some of the business logic is > > in xsp's, which is very annoying because it's not possible to extend one xsp > > from another, and it's quite difficult to do unit testing of them. > > > > Perhaps the original developers had good reasons to do so... > Or maybe they were working on an Alfa version of Cocoon, and had to do some > crazy stuff to work around some missing parts... They might have had changing > requirements all the time, or maybe a very tight time schedule... maybe they > wanted 900 days to finish the project, but only got 200? :-) > > Why don't you ask them? :-) > > [snip] > > Jan > > Jan Uyttenhove > Java Sofware Engineer > > [EMAIL PROTECTED] > > visit us @ http://www.xume.be > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
