On Apr 3, 2008, at 1:00 PM, Mike Schrag wrote:
The issue is that EOF's problem is not that it's CPU or memory bound, its problem is that it is a single-lock basically non- concurrent architecture.
Yes, now that Wonder has better stack synching between and within instances this might only be interesting if your stack has enormous memory requirements.
Using it for the appserver layer is potentially interestesting, but it's hard to get classloader separation within WO to be able to set it up properly.
Hmm. Ideally this could (among other things) enable persistent sessions, in that you might have an app instance (or collection of instances) running over a cluster whose members can join or leave the cluster without disruption.
tb _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
