I'm ok with JMS. I didn't think you could rewrite in such short of time.
Especially with Remoting and AOP just now becoming stable. I think this
email thread is good because it will allow us to determine whether or not we
can release. I still think there is enough functionality.
With respect to the cache. I have 3 major tasks that need to be done before it is ready:
1. [Bela] Implement pessimistic and optimistic locking
(transactability) on a cluster of caches. I should be done by mid
April with this
2. [Bill, Bela] (Stupid) integration into an Interceptor (AOP). Here
we need to flesh out some of the difficulties we encountered
talking on the phone today, e.g. instrumenting collections,
primitive types, recursive instrumentation of an object graph etc.
3. [Jeremy, Dain] Integration of the cache into the
PersistenceManager. The first version will have the
PersistenceManager use the Cache as a replicated in-memory cache.
Our use case will initially be shared DB, so all nodes use the
same database. At a later stage (probably not JB4) we will provide
unshared DBs. This involves some more efforts, e.g. retrieving
full DB state for new nodes (from existing nodes).Tasks #1, #2 and #3 can be done in parallel.
Although #1 is not yet done, the API will remain the same, so the Cache can already be used (without transactability though).
#2 requires some effort by Bill, and Bela (if locking is done before mid-April).
Task #3 will be done by Jeremy and Dain. I don't know what issues we will encounter there. Jeremy/Dain, can you comment on this ?
-- Bela Ban
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
