I have been plunging head first in to OOP (into a wall, I should say...) and I am trying to put all the pieces together so that I can begin implementation.
Anyways, I am wondering if I need a controller layer in my design pattern? I really don't like the idea of using a configuration file (xml or index.cfm) and wiring everything to it like a fusebox, so I am staying away from frameworks. I have been learning about seperating my business model into beans, DAO's, gateways and services and I think I like the abstraction that offers. However, it seems to me like my views can interact directly with the service, making a controller layer unneccesary. Is that correct, or am I lost again? P.S. I don't entirely understand what all a service does, so I do have some questions about the service layer, but I will start a seperate thread for that. I would have some questions about the facade layer, but I don't have a clue how to use that so I don't even know where to begin with the questions regarding that. Thanks, Aaron ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
