Posted by Erik Bruchez-3 on
URL: https://discuss.orbeon.com/Mysql-tp1395395p1472178.html

On Sat, Feb 6, 2010 at 2:39 PM, Jeremiah Jahn <[hidden email]> wrote:

>> 3. Regarding client state: we still don't recommend using it except
>> for the smallest pages, because exchanging full state through Ajax can
>> be very costly.
>
> Why did you deprecate the session based state?  Seems like it wouldn't be too bad for a relatively limited number of users.  And at the same time not require another pile of dependencies.  Or am I reading the above correctly, and you've gone with the idea that it's better to push things out of memory, and into exists?

We thought it was no longer acceptable to get errors about the state
being not found. So we rewrote/extended the "session" mode to fix that
and allow overflow to disk. Since it was no longer technically correct
to say that the state was stored in the session, we picked the name
"server" which reflects the reality better.

You are right that we added a dependency on eXist. But it would be
perfectly doable, and maybe desirable, to write a plain
filesystem-backed overflow mechanism. If you are tempted, check
XFormsPersistentApplicationStateStore.java.

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws