From: cvs@openprivacy.orgCVS update: sierra/docs
Date: Monday February 12, 19101 @ 0:11
Author: burton
CVSWEB Options: -------------------
Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi
View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs
-----------------------------------
Update of /usr/local/cvs/public/sierra/docs
In directory giga:/tmp/cvs-serv5373/docs
Modified Files:
CHANGELOG TODO
Log Message:
...
*****************************************************************
File: sierra/docs/CHANGELOG
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/CHANGELOG?annotate=1.3
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/CHANGELOG?rev=1.3&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/CHANGELOG.diff?r1=1.3&r2=1.2
-----------------------------------
Index: sierra/docs/CHANGELOG
diff -u sierra/docs/CHANGELOG:1.2 sierra/docs/CHANGELOG:1.3
--- sierra/docs/CHANGELOG:1.2 Thu Feb 8 18:42:48 2001
+++ sierra/docs/CHANGELOG Mon Feb 12 00:11:19 2001
@@ -1,8 +1,37 @@
********************************************************************************
-*** Last-Modified: $Date: 2001/02/09 02:42:48 $
-*** Version: $Id: CHANGELOG,v 1.2 2001/02/09 02:42:48 burton Exp $
+*** Last-Modified: $Date: 2001/02/12 08:11:19 $
+*** Version: $Id: CHANGELOG,v 1.3 2001/02/12 08:11:19 burton Exp $
*** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
********************************************************************************
+
+ - Sun Feb 11 17:21:55 2001 (burton@relativity.yi.org): (DONE) not every
+ component within Sierra needs or should be under the 'talon' package.
+ Instead we should move these to their own package... Example. The basic nym
+ package should be under org.openprivacy.sierra.nym.talon. The reputation
+ interfaces should go under org.openprivacy.sierra.reputation.talon.
+
+ - Sun Feb 11 16:39:52 2001 (burton@relativity.yi.org): (DONE) Need an
+ abstraction of how to create and manage nyms. The facility needs a way to
+ get the private and public keys for the nym and also determine a new nym
+ based on another nym. This "new" nym could be used temporarily but could
+ also stay with the user for a long period of time with support for the
+ parent nym proving that it created this sub-nym. The system should support
+ basic nyms which are simple to implement but scales to PGP, RSA, etc. When
+ it comes time to rewrite this Sierra to support PGP/RSA we shouldn't have to
+ modify any of Sierra to support this.
+
+ - need to provide an equals() method so that we can determine if two Ns are
+ the same.
+
+ - Nym implements Principal -> Talon interface
+ +init() do whatever it takes to build this Num
+ +getPrivateKey
+ +getPublicKey
+ +getNym() get a child nym... based on this nym
+
+ - KeyBuilder -> Talon interface... need to build more impls...
+ +getNym()
+ +getPropertyManager()
- Thu Feb 8 18:36:54 2001 (burton): (DONE) ReputationCalculationEngine should
throw Exceptions for every operation due to the fact that a RemoteRCE may not
*****************************************************************
File: sierra/docs/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.52
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.52&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO.diff?r1=1.52&r2=1.51
-----------------------------------
Index: sierra/docs/TODO
diff -u sierra/docs/TODO:1.51 sierra/docs/TODO:1.52
--- sierra/docs/TODO:1.51 Fri Feb 9 14:39:11 2001
+++ sierra/docs/TODO Mon Feb 12 00:11:19 2001
@@ -1,6 +1,6 @@
********************************************************************************
-*** Last-Modified: $Date: 2001/02/09 22:39:11 $
-*** Version: $Id: TODO,v 1.51 2001/02/09 22:39:11 burton Exp $
+*** Last-Modified: $Date: 2001/02/12 08:11:19 $
+*** Version: $Id: TODO,v 1.52 2001/02/12 08:11:19 burton Exp $
*** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
********************************************************************************
@@ -8,63 +8,29 @@
= PRIORITY
= ===============================================================================
-- should the SOAPServerRCE be pointed to another impl RCE which is local? This
- would be needed to make sure that the SOAPServerRCE works with a
- SOAPClientRCE.
= ===============================================================================
= BEGIN MILESTONES
= ===============================================================================
- - Need an abstraction of how to create and manage nyms. The facility needs a
- way to get the private and public keys for the nym and also determine a new
- nym based on another nym. This "new" nym could be used temporarily but
- could also stay with the user for a long period of time with support for the
- parent nym proving that it created this sub-nym. The system should support
- basic nyms which are simple to implement but scales to PGP, RSA, etc. When
- it comes time to rewrite this Sierra to support PGP/RSA we shouldn't have to
- modify any of Sierra to support this.
-
- - need to provide an equals() method so that we can determine if two Ns are
- the same.
-
- - Nym implements Principal -> Talon interface
- +init() do whatever it takes to build this Num
- +getPrivateKey
- +getPublicKey
- +getNym() get a child nym... based on this nym
-
- - KeyBuilder -> Talon interface... need to build more impls...
- +getNym()
- +getPropertyManager()
-
- determine requirements for a data store... maybe this *should* be
something like jewel.
+ - maybe we should remove putReputation from the RCE and just have an
+ event based system so that an RCE can be a target but so can a
+ RCEStore.
+
+ - ... this should just add a listener and they we can call methods to
+ see if it is something we need to pay attention to.
- need to build a Query type used to fetch an actual reputation value (not
getReputation). This should use the Hashcode of current objects.
- - not every component within Sierra needs or should be under the 'talon'
- package. Instead we should move these to their own package... Example. The
- basic nym package should be under org.openprivacy.sierra.nym.talon. The
- reputation interfaces should go under org.openprivacy.sierra.reputation.talon.
-
-
-
-
-
-
TODO:
- -
-
- - maybe we should remove putReputation from the RCE and just have an
- event based system so that an RCE can be a target but so can a
- RCEStore.
- Use Case: http://pix.comedia.com/OpenPrivacy/20010116/DSCN6054.JPG
@@ -166,6 +132,11 @@
= ===============================================================================
= END MILESTONES
= ===============================================================================
+
+
+- should the SOAPServerRCE be pointed to another impl RCE which is local? This
+ would be needed to make sure that the SOAPServerRCE works with a
+ SOAPClientRCE.
This archive was generated by hypermail 2b30 : Mon Feb 12 2001 - 00:11:50 PST
