New server-side option for XForms engine state

All,

The Orbeon PresentationServer XForms engine now supports options for
specifying where XForms engine state is stored: client-side, or
server-side.

Until now, state was always kept on the client. With client-side state
handling, when an (X)HTML page is produced, state information is
stored directly into the (X)HTML page. When Ajax requests are
performed between client and server, complete state information has to
travel back and forth.

With server-side state handling, state is kept in the user
session. This reduces the size of (X)HTML pages and the size of Ajax
requests, leading to faster page loads and lower latency over slower
connections.

Both approaches have benefits and drawbacks. Check out the
documentation for the details:

   http://www.orbeon.com/ops/doc/reference-xforms-ng#state-handling

In addition to server-side state handling, a state cache has just been
put in place, which helps making Ajax requests more efficient whether
client-side or server-side state handling is used.

Both those improvements are good steps toward better XForms
performance. Stay tuned for more!

-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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws