×
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.
From: Thorbjørn Ravn Andersen
Most likely you and your java colleagues have had many
more users than we did.
I don't know. Pete Helgren, who occasionally posts to this list would know more about it than I. He was a manager over the java team. I seem to recall that the company began imploding before most of the java applications gained much traction. The java team was laid off. The company now seems to be struggling to maintain a lot of disparate code bases.
I was wondering if you had any experiences to
share (except the one I would like to hear - namely that the
autoadjustment of OS/400 coped well with all stress situations :)
You and Walden made some good points about the scalability of this technique last week. And I don't have much information to refrute them, except the generalization that IBM i is good at managing many jobs reliability. But I have a hunch that this technique would NOT be best for a site that needed to accomodate thousands of concurrent users, who drifted in and out during the day.
Java is CPU intensive, and J2EE is really designed as a distributed architecture. It seems to me that you really need a server farm if you need to accommodate thousands of concurrent of users.
Nathan.
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
