This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Why are you restricting your possibilities to a component based framework? Is this some kind of business requirement? Personally when choosing a framework I go for the one that best meets the needs of my application. Just curious.
In all seriousness though, Jason is correct. Component based frameworks are all the buzz right now. Don't base a design decision on buzz words <clears-throat>ajax</clears-throat>. There is nothing wrong with good old fasioned request/response action frameworks. In fact, there is nothing wrong with not using a framework, if the project calls for it.