Hi, I'm thinking about (web) applications in terms of information systems (in an organizational context). Information systems take input (data), process it (classify, arrange, store, calculate) and then create output (data, dashboards, whatever). The output is then usually used as feedback for the next input. The next thing to note about information systems is, that they are situated/working in a defined environment (with suppliers, customers, competitors, stockholders, regulatory agencies etc.).
So lots of Agavi vocabulary I'd say: - three basic activities produce the information organizations need: - input - processing - output - feedback is output used to evaluate and refine the input. - environmental actors interact with the organization and its information system. Sooooo, coming to a conclusion with some sort of further hints: I'd say the action/view/model/template/cache/validation thingy is some sort of input->processing->output chain that uses the services of Agavi (the organizational unit in this case) like config, storage, routing, filter chain etc. to create output (web pages etc. with new links) that is used as feedback for new input. I think the earlier mentioned "processing unit" is not the worst suggestion. "Agavi Processing Unit" - APU (Nahasapeemapetilon!), "Processing chain" or similar perhaps? Even though it's not exactly a chain. Waiting for further suggestions. :) Thanks for reading. Regards, Steffen _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
