[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jboss-cvs-commits
Subject:    [jboss-cvs] jboss-cache/docs/design todo.txt
From:       Bela Ban <belaban () users ! sourceforge ! net>
Date:       2003-12-30 23:46:13
Message-ID: E1AbTYz-0006Vz-00 () sc8-pr-cvs1 ! sourceforge ! net
[Download RAW message or body]

  User: belaban 
  Date: 03/12/30 15:46:12

  Modified:    docs/design todo.txt
  Log:
  no message
  
  Revision  Changes    Path
  1.5       +6 -44     jboss-cache/docs/design/todo.txt
  
  Index: todo.txt
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-cache/docs/design/todo.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- todo.txt	26 Dec 2003 18:49:01 -0000	1.4
  +++ todo.txt	30 Dec 2003 23:46:11 -0000	1.5
  @@ -1,5 +1,5 @@
   
  -$Id: todo.txt,v 1.4 2003/12/26 18:49:01 belaban Exp $
  +$Id: todo.txt,v 1.5 2003/12/30 23:46:11 belaban Exp $
   
   
   
  @@ -39,7 +39,11 @@
   - Specify TreeCache and TreeCacheAop in a separate interface
     This serves better documentation
   
  -- Use of XID to replace the GlobalTransaction ID
  +- Use of XID to replace GlobalTransaction
  +
  +- Make TreeCache a JCA adapter (essentially a Resource manager), implement XMResource
  +
  +- Optimistic locking
   
   - Persistence for TreeCache (CacheLoader interface)
     updates are saved in stable storage. This is
  @@ -56,48 +60,6 @@
   - Resizing of cache at runtime
   
   - Investigate use of soft/weak refs for cache storage
  -
  -- Distributed lock manager with movable locks (Sacha):
  -  We need a distributed lock manager with movable-locks ;)
  -
  -  If you have the lock locally:
  -  - you lock locally
  -  - use the resource
  -  - you unlock locally
  -
  -  If you don't have the lock locally:
  -  - you find where is the remote lock (we can keep a cache)
  -  - you lock remotely
  -  - you use the resource
  -  - you unlock remotely
  -
  -  If you don't have the lock locally and you "detect" that you are a strong
  -  user of the lock (the DTM has to detect this), the lock is moved locally
  -  first and since then you only do local-locks. Very fast.
  -
  -
  -- Cache should be able to use multiple backend stores stacked in
  -  interceptor-like fashion, e.g.
  -
  -         Cache
  -           |
  -           |
  -  ReplicationInterceptor
  -           |
  -           |
  -  PersistentInterceptor
  -           |
  -           |
  -   StatisticsInterceptor
  -
  -  This should all be configuration-driven.
  -
  -
  -  Example: any method of the cache would be implemented by a dynamic
  -  proxy, which converts the typed method into an Invocation. The
  -  Invocation is then passed on to the first interceptor, which passes
  -  it on to the next and so on. The last interceptor returns a value
  -  (if retval is defined) and passes it back up the stack.
   
   
   
  
  
  


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
jboss-cvs-commits mailing list
jboss-cvs-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
[prev in list] [next in list] [prev in thread] [next in thread]