Joe Pluta skrev den 06-06-2008 14:37:
Which is why I say create a single connection at the beginning of the session and use it throughout. You need connection pooling when you have a stateless architecture that requires reconnection for every request.
By having a connection for every user session you may run into a scalability problem since you require the user to log out to regain the resources allocated to that connection.

By properly using a pool for connections you can have long session timeouts and short idle times for connection timeouts allowing you to serve more users on the same hardware.

This naturally requires that the backend calls are stateless - all needed information is passed from the session object - which you must do anyway since this is for web users.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.