×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
What's interesting to me about stateful sessions is that even with the
biggest IBM i you can purchase they are still finite as I understand it. By
that I mean the job number size is only six digits. That's not to say you
couldn't have a smart router on the front end sending requests to a "server
farm of IBM i's" (felt weird saying that btw :-).
I've always felt I was more productive when coding an application that was
stateful just because there are less things to think about, but then again
that would be comparing apples to oranges because my stateful coding has
mostly been in green screen and my stateless in the browser. Would be
interesting to write a stateless green screen app :-)
Aaron Bartell
On Fri, Dec 31, 2010 at 12:13 PM, Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx
wrote:
Yes I guess that is the concern. In a stateless environment I can have,
say, 10 threads/jobs managing 300 concurrent sessions. In a stateful
environment I would have 300 threads/jobs. Is it a problem? I am not sure.
With a 1000 concurrent sessions, is it just as efficient?
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.
midrange.com
