I noticed that the Hibernate DataSource examples tend to wrap any fetch, add, delete etc., method in a Hibernate Session open/close. Is is possible to use a DataSource in SmartGWT with the ‘OpenSessionInView’ strategy where a particular session maintains an open Hibernate session to take advantage of the L1 cache across different HTTP requests for the same user?
That strategy only makes sense in a server-oriented architecture where “session affinity” aka sticky sessions is required to get adequate performance. SmartGWT is a client-oriented architecture where caching takes place in the browser and zero server-side session state is required. That’s why it has radically better performance and can survive server crashes without losing any data and without requiring replication on the server.