|
By having a connection for every user session you may run into ascalability problem since you require the user to log out to regain the
Joe Pluta skrev den 06-06-2008 14:37:
request.
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
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.
--
Thorbjørn
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
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.