Yes, I used stateful pages in most of my applications - and for some of
them even heavily (e.g. 1 moved from Tapestry and 1 from JSF).
Hi,
Can you provide us some examples on how you used stateful pages in your
applications? What sort of
use cases were you facing that you needed a stateful page instead of a
stateless one?
It's not that "I needed" :), more that it was used in projects all over,
possibly because of:
- migration of apps from other stateful web frameworks.
- rewriting of desktop apps to web. For this, "Click + stateful + JS
libs" is close to Swing in many respects. Other find it even quite close
to VB productivity levels if there were have some sort of GUI builder :).
- "perceived simplicity" if everything is stateful. It takes lots of
effort for average developers to get used to the HTTP stateless model,
especially if they were doing desktop apps before.
- business people (the mighty "domain specialists" :) ) who also
"code" prototypes instead of just doing proper requirements and mockup
screens. They can't get the stateless model, and Velocity as at the
limit, but fortunately Click has both - yet :).
So to cut a long story short, our main use case is for intranet apps,
with known and limited number of users. It is not a problem to force the
latest browser version or the use of only one window per app, to have
that MDI l&f that users like in desktop apps.
regards,
Andrei.
