|
Maybe someone else can answer it better. Part of the problem seems to
be that OO terminology means different things in different circles.
But i've come to understood 2 things from listening in to all these
conversations over the past years. 1) the controllers / listeners in MII or MG should ideally be loosely coupled to your model. You should be able to pull your model out and implement it elsewhere fairly easily. 2) a service layer can help a lot where you need to get objects to work together. it's a means to coodinate and group small units of functionality together into a whole thing. a service also provides functionality for the app as a whole. in my mind, using the analogy of working with people, the boss (controller/listener) should direct teams and individuals. Sometime you need a team (a service) to get something done, or an individual to interface with many people (another form of a service) - and sometimes you need just an individual to do the job independently. But the boss/controller should only direct the teams, not participate in the work of a team/service. Does that make any sense? That's how i understand the differentiation at this point. Jeff Chastain wrote:
|
- [CFCDev] Calendar, Events, and CRUD Jeff Chastain
- Re: [CFCDev] Calendar, Events, and CRUD Matt Williams
- RE: [CFCDev] Calendar, Events, and CRUD Jeff Chastain
- Re: [CFCDev] Calendar, Events, and CRUD Matt Williams
- RE: [CFCDev] Calendar, Events, and CRUD Cody Caughlan
- RE: [CFCDev] Calendar, Events, and CRUD Jeff Chastain
- RE: [CFCDev] Calendar, Events, and CRUD Peter Bell
- Re: [CFCDev] Calendar, Events, and CRUD Matt Williams
- Re: [CFCDev] Calendar, Events, and CRUD Nando

