From: cvs@openprivacy.orgCVS update: talon/docs
Date: Wednesday February 28, 19101 @ 2:53
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/talon/docs
-----------------------------------
Update of /usr/local/cvs/public/talon/docs
In directory giga:/tmp/cvs-serv12866/docs
Modified Files:
DOCUMENTATON_TODO TODO
Log Message:
updated docs to reflect new website update
*****************************************************************
File: talon/docs/DOCUMENTATON_TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/DOCUMENTATON_TODO?annotate=1.4
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/DOCUMENTATON_TODO?rev=1.4&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/DOCUMENTATON_TODO.diff?r1=1.4&r2=1.3
-----------------------------------
Index: talon/docs/DOCUMENTATON_TODO
diff -u talon/docs/DOCUMENTATON_TODO:1.3 talon/docs/DOCUMENTATON_TODO:1.4
--- talon/docs/DOCUMENTATON_TODO:1.3 Fri Feb 9 02:44:13 2001
+++ talon/docs/DOCUMENTATON_TODO Wed Feb 28 02:53:45 2001
@@ -1,4 +1,26 @@
+********************************************************************************
+*** Last-Modified: $Date: 2001/02/28 10:53:45 $
+*** Version: $Id: DOCUMENTATON_TODO,v 1.4 2001/02/28 10:53:45 burton Exp $
+*** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
+********************************************************************************
+
+- Thin factory/component mechanism for managing components.
+
+- Pool/Singleton
+
+- Cross platform, cross project, cross licensing
+
+- Dual licensed BSD Style/GPL
+
+- central location for standard interfaces (logging, property management, etc).
+
+- all objects within the system have a unique URI.
+
+- objects can be served based on reputation and bias of the caller.
+
+- Talk about how it maintains object lifetime. Lifetime management.
+
- use of -Dtalon.project= for specifying which property file to grab.
- Example of creating a component. HelloWorldComponent
*****************************************************************
File: talon/docs/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/TODO?annotate=1.12
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/TODO?rev=1.12&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/talon/docs/TODO.diff?r1=1.12&r2=1.11
-----------------------------------
Index: talon/docs/TODO
diff -u talon/docs/TODO:1.11 talon/docs/TODO:1.12
--- talon/docs/TODO:1.11 Sat Feb 24 21:47:45 2001
+++ talon/docs/TODO Wed Feb 28 02:53:45 2001
@@ -1,23 +1,47 @@
********************************************************************************
-*** Last-Modified: $Date: 2001/02/25 05:47:45 $
-*** Version: $Id: TODO,v 1.11 2001/02/25 05:47:45 burton Exp $
+*** Last-Modified: $Date: 2001/02/28 10:53:45 $
+*** Version: $Id: TODO,v 1.12 2001/02/28 10:53:45 burton Exp $
*** Author: Kevin A. Burton ( burton@openprivacy.org )
********************************************************************************
+ - Need to have an implementation of the Java Versioning Specification within
+ components. http://java.sun.com/j2se/1.3/docs/guide/versioning/spec/VersioningSpecification.html
+
+ - can we provide this information with standard
+
+ Component meta-info
+ Interface -> title, vendor, description, version
+ Implementation -> title, vendor, description
+
+ Major version numbers identify significant functional changes.
+ Minor version numbers identify smaller extensions to the functionality.
+ Micro versions are even finer grained versions.
+
+
+ getImplementationTitle()
+ Return the title of this package.
+
+ getImplementationVendor()
+ Returns the name of the organization, vendor or company that provided this implementation.
+
+ getImplementationVersion()
+ Return the version of this implementation.
+
+ getSpecificationTitle()
+ Return the title of the specification that this package implements.
+
+ getSpecificationVendor()
+ Return the name of the organization, vendor, or company that owns and maintains the specification of the classes that implement this package.
+
+ getSpecificationVersion()
+
+
- We need a new method in Component and ComponentHandle, getLifetime()... this
could return a Lifetime object and if it is null it is up to deployment what
the lifetime is. This can be used so that a Component can REQUIRE that a it
has a certain lifetime. The Lifetime object should have a method
getInstance() which would return one of its known instances.
- - Sat Feb 24 21:40:05 2001 (burton@relativity.yi.org): All components within
- the system should have a unique URI.
-
- - Mon Feb 19 18:47:43 2001 (burton@relativity.yi.org): (DONE) support the
- concept of nested Exceptions.... A TalonException should support a
- constructor which is passed an Exception. When the stack is printed it
- should also print the reason Exception.
-
- Make sure to warn(and disallow) if Talon has registered more than one component with the
same name.
@@ -28,6 +52,9 @@
interface. It is possible that we can have multiple implmenentations
registered which implement the same interface. Duh!!!
+ - this mechanism should be fixed so that we can specify a default component
+ for a interface or serve them based on reputation.
+
- should we build a simple assertion mechanism from Arrowhead???? Maybe
Arrowhead should use Talon and then it will get assertions?
@@ -41,52 +68,13 @@
first starts up). This should increase performance of objects due to
reduced component instantiation time.
- - each component needs a mechanism to register its own properties.
-
- Talon should be able to use its own Components without causing holes in the
system?????
- - Cross platform, cross project, cross licensing
-
- - Dual licensed BSD Style/GPL
-
- - Thin factory/component mechanism for managing components.
-
- - Pool/Singleton
-
- - Question... what do I do about the interface??
-
- Initializes itself on request. Basically just a snap-in library that any
application can use.
-
- - Throw Exceptions if the object is not available
-
- - Method to deliver properties to a component.
-
- - XML component/object deployment mechanism.
-
- - Serve up Component objects
-
- - CompomentManager
-
- - getInstance() releaseInstance( Component comp )
-
- - If the object is a Singleton releaseInstance is redundant. It is
- necessary if it is a pool
- - Support the ability to obtain an object by a Handle... Example... files,
- URLs, etc.
-
- - Ship with some basic interfaces.
-
- - Logger (Singleton)
- - BasicTextLogger
- - Log4JavaLoggerImpl
-
- - PropertyManager
- - Implementations:
- - PropertyFileManager... properties backed by a file.
-
+
- ObjectPool
// get the number of objects available for use.
@@ -98,16 +86,6 @@
// get the maximum number of objects to serve.
- getMaxCount()
-
- - Need to have a ComponentHandle object so that we have tight bindings between
- properties and handles.
-
- - NotAvailableException if the Factory can not serve this.
-
-
- Object count handling. Singleton, handle (one singleton per handle) or
Named Singleton, pooled (100, 200, etc), infinite (handled by the garbage
collector)...
-
-
- - Define property configuration mechanism. See src/config/talon.properties
This archive was generated by hypermail 2b30 : Wed Feb 28 2001 - 02:53:46 PST