On Nov 23, 2008, at 7:39 AM, dododo2020 dododo2020 wrote:
Don't you think terracotta's approach can enhance WO significantly
with or without EO?
I don't think terracotta is that interesting at the EOF layer. It
might be useful if applied to WOSessions. There's been some discussion
of this in the past, enabling persistent sessions such that app
instances can leave and reenter the cluster without disrupting
anyone's session. But you'd have to isolate your WOSessions and
there'd have to be pretty strict rules about what you put in there.
I'm not sure this is possible to solve in the general case.
1) Having caches for each instance is not efficient. Sharing cache
is the best.
Depends on your app. For many cases I believe shared cache would lead
to contention and less throughput. Memory is cheap. If you need to
synchronize instances there is a reliable mechanism to do so.
3) EOF may use String and Hashtable for many internal processes.This
may slow the app.
I want a compact-transparent solution to be learned in a short time.
There are examples of WO applications scaling to massive size. Strings
and Hashtables aren't the choke point. Could these things be made more
efficient? Certainly. But in practice it's not an issue.
tb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
