Exactly what I wanted to know.
Basically, I want to be able to easily apply pre-processing and post-processing logic to a simple script without relying on any Apache-specific mechanisms.I'm not talking about specific functionality using an enterprise level web application framework like WACT. I'm talking about general functionality in a typical PHP script.
This seems out of scope based on you saying you want to keep it simple. Code morphing (to me) means having a script that is managed by another script. When conditions or requirments change the controling script will edit the (pagecontroller's)code. It's easier than it sounds. Think of a Template view that saves to file insted of echoing to screen and thats how I would do it.
10. Ie. Authentication or Pagecaching may not happen on EVERY page so how do you plan to expand on this idea when the site grows in size and Page Controllers? Code morphing?
Good point. Code morphing? What's that? Sounds complicated. I'm not sure how exactly I'm going to handle it. I'll probably either use a central config file, or do something per page.