The most common pattern in a multi-user client/server application is session-per-request. In this model, a request from the client is sent to the server, where the Hibernate persistence layer runs. A new Hibernate Session is opened, and all database operations are executed in this unit of work. On completion of the work, and once the response for the client has been prepared, the session is flushed and closed. Use a single database transaction to serve the clients request, starting and committing it when you open and close the Session. The relationship between the two is one-to-one and this model is a perfect fit for many applications.
Subscribe to:
Post Comments (Atom)
-
Interface: only know the customer requirement and don't know the implementation than go for interface. Advantage: 100% abstrac...
-
Now a days in interview interviewer always ask questions related to Collection and map And they also ask why map interface is not child of...
-
If you want to share or update the same data then the activity must be synchronized to avoid the error.in java using synchron...
No comments:
Post a Comment