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

List:       jboss-cvs-commits
Subject:    [jboss-cvs] jboss-cache/docs TODO
From:       Bela Ban <belaban () users ! sourceforge ! net>
Date:       2002-12-31 22:54:08
[Download RAW message or body]

  User: belaban 
  Date: 02/12/31 14:54:08

  Modified:    docs     TODO
  Log:
  *** empty log message ***
  
  Revision  Changes    Path
  1.9       +5 -1      jboss-cache/docs/TODO
  
  Index: TODO
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-cache/docs/TODO,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- TODO	31 Dec 2002 22:43:26 -0000	1.8
  +++ TODO	31 Dec 2002 22:54:07 -0000	1.9
  @@ -1,4 +1,4 @@
  -$Id: TODO,v 1.8 2002/12/31 22:43:26 belaban Exp $
  +$Id: TODO,v 1.9 2002/12/31 22:54:07 belaban Exp $
   
                  Todo list / requirements for Cache/JBoss
                  ----------------------------------------
  @@ -14,6 +14,10 @@
   - Implement those interfaces. Start off with
     org.javagroups.blocks.TransactionalHashtable for replication side of
     things
  +
  +- Implementation: one JavaGroups channel per cache, or do all caches
  +  use the same channel ? Can we reuse the channel used by the
  +  Clustering subsystem ?
     
   -  Check whether we should make transactions explicit in org.jboss.cache.Cache; ie. instead of
      associating them with the current thread, we should explicitly specify Xids
  
  
  


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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]