Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently I’m using a session-per-request approach to manage Hibernate sessions in a Java web application. I heard the term session-per-conversation thrown around and was wondering what situations it suits and what benefits it can bring over session-per-request?
One of the main benefits I’ve experienced is that you can implement behavior where not every change should directly be committed to the database — Session per conversation will allow you to set up objects over multiple requests, and only commit to the db on the final ‘yes I really want to do this’ action. Typical scenarios for this are things like booking a hotel room using a wizard-like series of pages.