Since this is a theoretical discussion, maybe stating some of the basics regarding HTTP would not be unwelcome.
1. WEB MVC STRUCTURE: The difference between standalone and web applications in relationship to the MVC framework is that standalone applications have components on screens which communicate with the rest of the framework but the entire screen (page) communicates with the rest of the framework. 2. WEB MVC DATA: Since this is so, very different types of information are sent back in a sort of "flood" to the framework, e.g. (a) "plain" data such as credit card numbers, how many widgets the user wants, etc.; (b) "controller" data such as what handler should be used; (c) "processing" data such as what method to call on the handler; (d) "presentation" data such as what colors to make the screen, what layout to use on the screen, etc., which can take many different forms and which can relate to the serverside in many different ways; (e) etc. The types of data breakdown here is indefinite and framework related. Given this much, what does the following mean? > Joe Germuska wrote the following on 2/18/2005 12:32 PM: > > Ted and Vic, in particular, are saying that commons-chain is a good way > > to write one of these applications-which-has-nothing-to-do-with-HTTP. -- No one ever went blind looking at the bright side of life. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
