The controller exists, in part, to marshal user input and external values into the model. Your model would have no idea as to the origin of those values, and rightly should not. So accessing shared scopes in the controller would be fine.
Dw On Tue, Apr 29, 2008 at 12:03 PM, Charlie Griefer <[EMAIL PROTECTED]> wrote: > > Hey all... > > I've had a lingering question, and a thread over on cf-talk (about > properly encapsulating CFC methods) has really got me thinking about > it. > > Over on that thread, there's a "debate" (to use the term loosely) on > accessing the application scope from within a CFC. Yes, I understand > that's a "bad thing" and I understand why. But in an MVC framework... > what about CFCs in your controllers? Those CFCs don't really model > any particular object. They're more of a transport mechanism to > facilitate communication between the model and the view. > > So, I get that CFCs in the model should be encapsulated. But what > about CFCs in the controller? is it "acceptable" (which i realize is > a subjective term) to access shared scopes like application and > session from controller CFCs? > > -- > Evelyn the dog, having undergone further modification pondered the > significance of short-person behaviour in pedal depressed, > pan-chromatic resonance, and other highly ambient domains. "Arf," she > said. > > > > -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
