Session locking (introduced in 5.4) should be optional

Tapestry 5.4 introduced session locking, whereby access to the HttpSession is serialized when multiple threads are active for the same session (this can occur in some Ajax scenarios). This has been highly controversial, and (at the very least), it should be optional, controlled by a configuration symbol.