AfflictionNetworks/samskivert
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Edits.

Browse Source 
git-svn-id: https://samskivert.googlecode.com/svn/trunk@226 6335cc39-0255-0410-8fd6-9bcaacd3b74c
This commit is contained in:
mdb
2001-08-11 22:01:57 +00:00
parent 666afaaa93
commit 6cd3d23d7d
1 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
projects/samskivert/README
+17 -17
View File
@@ -1,25 +1,25 @@
The samskivert Project The samskivert library
---------------------- ----------------------
The samskivert Project (TSP) aims to provide useful reusable Java routines The samskivert library (SL) aims to provide useful reusable Java routines
that do things for which I've been unable to find useful reusable that do things for which I've been unable to find useful reusable
implementations on the net. implementations on the net.
Given the emphasis on reusability, TSP attempts to closely adhere to the Given the emphasis on reusability, SL attempts to closely adhere to the
following principles: following principles:
* Each individual module should depend as little as possible on other TSP * Each individual module should depend as little as possible on other SL
modules. Obvious exceptions include modules that are a logical extension modules. Obvious exceptions include modules that are a logical extension
of other modules and modules that clearly require a service that is of other modules and modules that clearly require a service that is
implemented by another TSP module and would have to implement that implemented by another SL module and would have to implement that
service themselves in the absence of dependence on the other module. service themselves in the absence of dependence on the other module.
* Modules should be both simple to use and as general purpose as possible. * Modules should be both simple to use and as general purpose as possible.
To meet these two competing requirements, a balance must be struck at To meet these two competing requirements, a balance must be struck at
that sweet spot where reusability is maximized. that sweet spot where reusability is maximized.
* Code included in TSP will freely depend on JDK packages available in the * Code included in SL will freely depend on JDK packages available in the
Java 2 platform and beyond. TSP is initially a repository of software Java 2 platform and beyond. SL is initially a repository of software
useful for server-side or stand alone applications and therefore need useful for server-side or stand alone applications and therefore need
not compromise because it needs to function in the JVMs of commonly not compromise because it needs to function in the JVMs of commonly
available web browsers. available web browsers.
@@ -27,29 +27,29 @@ following principles:
* We are not here to reinvent the wheel, nor to provide a uniform * We are not here to reinvent the wheel, nor to provide a uniform
interface to every software service under the sun. If something is interface to every software service under the sun. If something is
available in a freely redistributable and reusable form from someone available in a freely redistributable and reusable form from someone
else, it won't be found in TSP. If TSP depends on such software from else, it won't be found in SL. If SL depends on such software from
another source, it will provide clear documentation on how to get that another source, it will provide clear documentation on how to get that
software and make use of it within the scope of TSP's particular needs. software and make use of it within the scope of SL's particular needs.
Again a balance of reusability will be struck here and software that is Again a balance of reusability will be struck here and software that is
sufficiently difficult to make usable in an arbitrary environment will sufficiently difficult to make usable in an arbitrary environment will
not be used by TSP and may be "reinvented". not be used by SL and may be "reinvented".
Distribution Distribution
------------ ------------
TSP is released under the GPL. The samskivert library is released under the GPL.
Contribution Contribution
------------ ------------
Contributions to TSP are welcome. Control of the CVS repository is Contributions to SL are welcome. Control of the CVS repository is
presently in the hands of TSP's creator, mdb@samskivert.com and presently in the hands of mdb@samskivert.com and submissions will be
submissions will be reviewed prior to inclusion. Facilities for management reviewed prior to inclusion. Facilities for management of major
of major contributions by external parties will, of course, be provided contributions by external parties (ie. publicly accessible CVS server)
when such contributions exist. will be provided if circumstances dictate.
Contact Information Contact Information
------------------- -------------------
The person primarily responsible for TSP is Michael Bayne and can be The person primarily responsible for SL is Michael Bayne and can be
contacted at <mdb@samskivert.com>. contacted at <mdb@samskivert.com>.