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
instanc
I was toying with idea to use Terracotta as a possible clustering
solution for Cayenne ORM. Thought it can be used selectively for the
"cache" parts of the stack. But there are better, more targeted ways
to do cache syncing. The other thing - reattaching to the cluster
would only require te
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 b
Yeah, I gave some thought to this a while back (but didn't actually do
it) ... 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. Distributing it with Terracotta just causes
MORE lock contenti
(Sorry if this comes through twice, first version seems to have been
eaten.)
Has anyone done any investigation into using Terracotta with EOF?
I didn't find anything but wanted to make sure before I dig in.
tb
___
Do not post admin requests to the l
