While I do what to see use look at various frameworks, lets not forget the model side of the pattern. Most of these tools don't provide the model infrastructure. This is where we send most of type developing. This is where I have the most problems. IHMO, I'm not alone here. I know I'm always feeling like I've over-engineered my model. Typically, that most client don't appreciate the sophistication. For example, my current project uses the Row Data Gateway pattern, see http://martinfowler.com/isa/rowDataGateway.html. This creates three classes. Since I want this to act as a component, I need two more classes. It just seems that I end up adding extra complexity. I'm not sure that it is always needed.
I'd like to see people mention or talk about various techologies that they used successfully much like Vic talks about his basejDAO library. I'm not suggesting that we fill the list with database topics, but it nice to share pointer and links. One thing I've been considering doing is writing up an article with an example using the Row Data Gateway pattern. Then, ask people for comments on how to improve it. Regards, Jeff _______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.com:8081/mailman/listinfo/mvc-programmers
