Travis
On 3/28/06, Werner Punz <[EMAIL PROTECTED]> wrote:
Travis Reeder schrieb:
> http://www-128.ibm.com/developerworks/java/library/j-cb03216/?ca=dgr-jw22StatelessWeb
>
> It would be interesting to take a look at working this type of thing
> into MyFaces. We are already doing some of this stuff with the session
> state saving to help with the back button, but I wonder if it could be
> taken a step further and persisted for long periods. It could go a long
> way in making JSF more scalable.
>
Ok to think this over:
It is sort of there already as you mentioned...
the persistence for long periods of time is problematic.
If you keep it in ram, it will suck up ram in no time.
If you drop it into a storage (file database etc...) it will
suck away your performance, unless you have the continuation fault
lenient (which means it does not matter if you can lose one point in
time), so that you can push it into an asynchronous backend process with
heavy caching in between.
I think getting a stateful approach is better done the way shale
and seam do it, by using the session for keeping conversations open in time.
That does not resolve the back button issue however.
