That's what I figured out myself. Basically when the code can get called from several places...
Thanks, -Yves- On 5/10/05, Kent Tong <[EMAIL PROTECTED]> wrote: > Yves Sy <yves.sy <at> gmail.com> writes: > > > > > Its very common yet you couldn't give a straight answer! > > > > I AM bothered because I'd want some convention on where to put logic > > (actually, controller logic NOT biz logic), or at least a rule of > > thumb that everyone on a team should follow. I wouldn't want one guy > > to do something one way and another guy doing it another way... > > well, if you really want a straight answer, you can apply > the following simple principle: Do you have duplicate code? > If yes, extract it to put it where it belongs. If no, the > logic is probably in the right place. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- A bus station is where a bus stops. A train station is where a train stops. On my desk I have a work station... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
