PHP is mostly used for web pages, which are transactional - the client
requests a page, the server runs a script, the script sends output to
the client, and the script ends. There is little need for thread
pooling or processing queues in such an environment.
Now that is not to say there isn't a reason to use MVC with PHP. It can
help simplify code by separating the business logic from the display
logic. There are a number of good frameworks around, but I don't know
much about them (I personally don't use any - I built my own years ago,
before any decent ones were available).
But choosing a framework is a personal decision. What you like, I might
hate, and vice versa. You will probably get all kinds of answers here.
My suggestion is to google for php mvc frameworks and take a look at
them for yourself. The page at
http://mashable.com/2014/04/04/php-frameworks-build-applications/#SLafsaQzSkqA
is a couple of years old, but has good information for a start.
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstu...@attglobal.net
==================