Hi Tapestronians, After a year of programming on a pernonal web project, I found that the time has come to do some refactoring. One of the subsystems that really need to be looked at is hibernate. I'm trying to decide on a pattern.
I was thinking about finding some inspiration in kickstart but I came across this : >It has proven suitable for low to medium load (some 100 concurrent users) >web-apps typically >found on corporate extranets. It's characteristics are... Is session-per-request typically capable of handling higher loads? Does anybody have an example implementation of session-per-request? Or, where can do the creation and the closing of the session best in tapestry. I dit found a class on the Hibernate site that provides the functionality to manage the sessions (create, get, close) per thread. And, by the way, if you would use non-blocking IO such as in Jetty, what would the impact be? Failure probably. Thanks, Lennart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
