On Jan 13, 2008 3:41 PM, Baz <[EMAIL PROTECTED]> wrote: > I'm in the same camp as both of you. So lets look at a situation where for > one event you interact with a USER in the session scope, but for other > events the USER is created on the request.
Those would be two different APIs on the service. One deals with the current user (as a facade to where it is stored). The other deals with access to a specific user. As others have said, controllers should be dumb, services (and domain objects) should contain all the logic. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
