On Fri, 18 Mar 2005 11:40:49 -0000, Pilgrim, Peter <[EMAIL PROTECTED]> wrote: > I think we are singing from the same hymnsheet, but > obviously different styles. You are talking about > abstracting away dependencies from MVC frameworks. > You have a use-case for wanting to switch at > a moments notice from Struts to Webwork and back > again.
I'm not sure if Konstantin has that use-case in mind, but I sure do. :) Another likely example would be sharing business and control logic between Struts Classic to Struts Shale. Or between a Java Web application or a ASPX application or a PHP application. We need to do all the same things for all the same reasons, but each of these framework wants to handle common tasks, like input validation, data conversion, and text formatting, on the presentation layer, and then leave the logic processing as an exercise to the developer. Another strategy would be to use the presentation layer to gather input values, and other state values, bundle it all into a context, and hand off to a business control layer for processing. The business control layer validates input, converts data, formats text, and (if appropriate) processes business rules and persistence logic, and returns the result to the presentation layer. What's left for the presentation layer is bundling values into the context, calling the command associated with the context, checking the state of the context for navigational semaphors, and rendering whatever values are returned. Everyone I talk to agrees that the presentation layer coding is where all the time goes. So, the challenge is to keep the presentation layer as simple and clean as we can by pushing the complexity up to the business control layer. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
