By dev.stonez
via industrieit.com
Published: Dec 01 2011 / 04:21
es, component oriented development will be the major pattern for web development. But the ‘components’ are going to be objects sitting on the client browser, written in JavaScript. The sweet spot for full blown JSF has therefore, IMHO, passed. The idea of requiring server interaction for most DOM changes is already starting to seem like it came from another age. Will there actually be any server-centric web framework in common use for new business web apps in the not too distant future?
However, corporate environments always have a legacy base of software preventing rapid change. Many of you have an existing investment in JSF or desire to remain with the JEE standard. We need to provide a mechanism where JSF can be used as a lightweight compositing mechanism, with very low CPU and memory overhead if desired, in order to transition to a more client side approach to web development.
Comments
henk replied ago:
This is really interesting. It's not just stateless JSF as-in not making use of a session, it's also pooling of page instances and being able to set this per page.
And associated spec issue has also been created for this: see http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1055
Voters For This Link (15)
Voters Against This Link (0)