transmission line noise

home

php.mvc

26 Dec 2008

Tagged with Miscellaneous

“php.MVC imple­ments the Model-View-Controller (MVC) design pat­tern, and encour­ages appli­ca­tion design based on the Model 2 par­a­digm. This design model allows the Web page or other con­tents (View) to be mostly sep­a­rated from the inter­nal appli­ca­tion code (Controller/Model), mak­ing it eas­ier for design­ers and pro­gram­mers to focus on their respec­tive areas of expertise.

The frame­work pro­vides a sin­gle entry point Con­troller. The Con­troller is respon­si­ble for allo­cat­ing HTTP requests to the appro­pri­ate Action han­dler (Model) based on con­fig­u­ra­tion mappings.

The Model con­tains the busi­ness logic for the appli­ca­tion. The Con­troller then for­wards the request to the appro­pri­ate View com­po­nent, which is usu­ally imple­mented using a com­bi­na­tion of HTML with PHP tags in the form of tem­plates. The result­ing con­tents are returned to the client browser, or via another pro­to­col such as SMTP.

php.MVC is a PHP port of Jakarta Struts. It cur­rently sup­ports many fea­tures of Struts, includ­ing declar­a­tive appli­ca­tion con­fig­u­ra­tion via the XML digester. For exam­ple, map­pings from the var­i­ous Action busi­ness logic com­po­nents to appro­pri­ate results pages can be spec­i­fied declar­a­tively in the XML con­fig­u­ra­tion file.”

more php.mvc

comments powered by Disqus