Hi, I've been through the documentation and tutorials, and this thing won't congeal in my head.
I'm really confused about the division of logic. For instance in the VLib tutorial application, a lot of the server-side lookup plumbing is in the Engine class, I have no idea why. And apparently page flow is handled directly in the code (that may or may not be a negative, I'm trying to decide). What I do understand is that the visit class holds session-type information. And I understand the mechanics of how to build components (the tutorial was very clear about that). But I have a bunch of why-type questions. I'm coming from a Struts world and the benefits of its MVC paradigm and the decoupling that gets you are very clear in my head. When I look at tapestry code what I think I see is an event-driven model, but the separation of concerns/duties is not so clear to me. So, I guess my first question is, what do people on this list see as the basic responsibilites of various sections of this framework? For instance is the Engine class supposed to handle interaction with the business layer, as in VLib? (if so that could result in a very large class). Regards, Steve ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
