Aaron wrote: <i>I still get the feeling this approach is designing a
system based on how a Windows sys admin would approach the situation. </i>
That's because I was describing current conventional wisdom :), which
like you say is a PC farm.
If one iseries can do it we can go to 32K sessions per web app system.
But all I'm saying is that as loads go up high enough you can have
multiple smaller iseries handling CGI with maintained state where the
session was logged in and DDM'ing to a database server.
Certainly not an issue, the important point is that stateless still has
a bottleneck in that there is *a* database server to store state even
though the "farm" is stateless. Maintaining state on the iseries is just
not deferring state to the database server, which would be on the same
box with an iseries, opening up another level of efficiency over status
quo farm systems.
rd
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.