On May 23, 2006, at 7:31 PM, Aristedes Maniatis wrote:
On 24/05/2006, at 8:03 AM, Sacha Michel Mallais wrote:If you actually want to handle 1 million concurrent users, then you're completely on your own: I doubt that has ever been done with anything, certainly not with WO.Google is probably somewhere up around that number. And how do you know this guy isn't rewriting the Google front end in WebObjects? :-)
Perhaps, but then again, Google's speed would certainly not be limited by WO. Even your garden variety business apps are more likely to be bound by the database's IO than the CPU of the app server.
I've always wondered what 'concurrent users' means in a web application. Live sessions? Page requests which come in the same time period as another page request is being processed? If the latter, then concurrent users will go up as the web site becomes slower due to load. If the former, what does it mean if you only use direct actions and don't create sessions?
In a WO app, it means sessions. If you don't use sessions, you've traded space (less) for speed (slower) or space (less) for functionality (less). If you choose to make that trade, a "concurrent user" would be the time that the app took to process the request, since that is basically a degenerate session of a single request.
sacha -- Sacha Michel Mallais Code Sculptor Global Village Consulting Inc. http://www.global-village.net/ PGP Key ID: 7D757B65 AIM: smallais Roses are #FF0000, violets are #0000FF, all my base are belong to you.
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
