The two-phase life cycle model is a strange beast to explain to web developers. The most often heard complaint is that this model is quite unnatural for web developers. Why would any web developer want to split the simple GET and POST requests into "render" and "action processing" phases so that some portal can render it correctly?
-
The simplest way to detect DoubleClick in Silverlight
-
Testing Frameworks for Java with Code Samples
-
An Essential Guide To WordPress SEO - Part 2
-
15+22 jQuery Image Slideshow/Slider Tutorials and Plugins for Your Next Projects
-
Web Server and Web Browser 2 in 1 Opera v10.10:
-
JavaSign: NetBeans Platform: Output windows in simple words
Comments
kayess replied ago:
I've written about this issue myself at http://www.kirit.com/The%20%E2%80%9CCorrect%E2%80%9D%20way%20to%20process%20forms
There are a few other things to think about (see my article), but I do like the diagrams on this one.
rick replied ago:
It seems so clear that we NEED something like the portlet model, but one would certainly hope for applicable standards to make it easy to use. The portlet experts I know all seem to agree that the initial Java spec doesn't cut the mustard, but I really don't know how much consensus there is about precisely how it needs to evolve?
fnord replied ago:
We need something like the portlet model? Why, oh why?! Please elaborate. ;) I haven't found much use for it myself, other than using it to push more stuff at the customers, that they don't need and would be better off without.
Voters For This Link (7)
Voters Against This Link (0)