I've done a similar thing by using an Events and Subscribe system, my controller abstract has a number of event broadcasts throughout, and it's very simple to build a subscriber that latches on to whatever it needs to in order to satisfy the business rules. I based mine upon some code I found through the googles, I've just now quickly tried to find it again with no success, I suppose though I could be convinced to package up what I've done and post it somewhere.
On Wed, Dec 2, 2009 at 8:41 PM, Diego Potapczuk <[email protected]> wrote: > Exactly. > > > ::: Diego Potapczuk > > »» Analista de sistemas > »» Tel: (71) 3287-8343 / (71) 9144-3062 > »» http://www.diegoliveira.com.br > > > > On Wed, Dec 2, 2009 at 9:22 AM, Vincent de Lau <[email protected]> wrote: > >> Consume basically means 'one object using another object'. >> >> Basically what it boils down to, is that you should move the code from the >> controller to an object in the Model layer (a Service is suggested). Both >> controllers can than consume/use this service to get their work done. >> >> Controllers should be thin and use Models to do the work. I can suggest >> reading http://www.survivethedeepend.com/ for more information on the >> subject. >> >> Vincent de Lau >> [email protected] >> >> > -----Original Message----- >> > From: tonystamp [mailto:[email protected]] >> > Sent: Wednesday, December 02, 2009 12:34 PM >> > To: [email protected] >> > Subject: Re: [fw-general] "observe" controller action >> > >> > >> > Thanks for the reply, but could you elaborate a bit more- what do you >> > mean by consume? >> >> >
