gnue/geas README doc/overview.txt

[Reinhard Mueller]

CVSROOT:        /cvs
Module name:    gnue
Changes by:     Reinhard Mueller <address@hidden>       01/06/10 11:56:44

Modified files:
        geas           : README 
Added files:
        geas/doc       : overview.txt 

Log message:
        Prepared README files for upcoming release

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/geas/README.diff?cvsroot=OldCVS&tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/geas/doc/overview.txt?cvsroot=OldCVS&rev=1.1

Patches:
Index: gnue/geas/README
diff -u gnue/geas/README:1.5 gnue/geas/README:1.6
--- gnue/geas/README:1.5        Mon Feb 12 14:40:08 2001
+++ gnue/geas/README    Sun Jun 10 11:56:43 2001
@@ -1,125 +1,19 @@
-GEAS : Gnue Enterprise Application Server
-=========================================
+This is GEAS, the GNU Enterprise Application Server, a part of GNUe, the
+GNU Enterprise project.
 
-The GNUe Application Server manages business objects for enterprise business
-systems. A range of planned features will be available automatically to any
-application that uses the GEAS server.
+GEAS lets you define arbitary persistant objects. GEAS will manage saving
+the data in a relational database, and calling of methods.
 
-For the user of an application, the existance of GEAS is not important -
-system administrators will have set it up so that their applications can
-easily find an appropriate server.
+GEAS is actively being developed. Please refer to the file named 'NEWS' to
+see which version you are looking at here, and what has changed since earlier
+versions.
 
-For application authors, the principal advantage of GEAS will be the ability
-to easily create applications with complex features. Once the full system
-has been implemented, a distributed and scalable system can be built with
-the same ease as a typical single user application. A transactional scalable
-multi user application will only need to consider the work that needs to be
-done: managing network access, all data storage, and the distribution of the
-work will be handled by GEAS.
+To install GEAS on your system, follow the procedure described in the file
+'INSTALL'.
 
+GEAS is free software. See the file 'COPYING' for the terms and conditions
+for copying, distribution and modification.
 
-Code Documentation:
--------------------
-Doxygen (http://www.stack.nl/~dimitri/doxygen/) is being used to create
-HTML, RTF and LaTex documentation from source code. To create the
-documentation, download and install doxygen, then run
-'doxygen geas.doxygen.cfg' in the gnue/geas/ directory. It will create
-appropriate directories and files in the 'doc/code' directory. (Soon, this
-should be automatically done by automake, if doxygen is available.)
-
-
-Current features:
------------------
-       Manage business objects for storing data. Objects may contain
-references to other objects, sets of objects, and look up data from other
-objects.
-
-       SQL database independance: Currently MySQL is used for data storage,
-with PostgreSQL support planned soon, and later libGDA will be used to allow
-any supported database to be used for storing data. Custom database systems
-will be able to be added with minimal effort.
-
-       Language independance: While Python is the main language for GNUe
-applications, any language can be used to write a GEAS client, and object
-methods will be able to be written in any language. This also means that
-adapting existing software to use GEAS will not have the additional burden
-of language differences.
-
-
-Planned features (short term):
-------------------------------
-       Business object methods: Allow business objects to contain code to
-perform arbitrary operations, and code to enforce business rules.
-
-       More advanced searching: The Object Query Language offers the power
-of SQL-92, combined with a range of features specific to object based
-systems. This will allow applications that need it to perform complex data
-operations. OQL will be implemented a step at a time, with parts of the
-system being done at different times, leading to a gradual.
-
-
-Planned features (long term - not in any particular order):
------------------------------------------------------------
-       Security : All access to the system will be automatically controlled
-and monitored with exact details able to be controlled by the system
-administrator. The intention is to allow access to be controlled to fine
-levels of detail: even particular fields in particular objects will be able
-to be controlled individually.
-
-       Database independance : A data integrator will allow data to be
-transferred between GEAS and other systems, both as a batch mode operation,
-and on demand in real time.
-
-       Transaction support : Many business operations require features
-offered by standard transaction based systems. GEAS will provide a simple
-and standard mechanism for managing transactional data access.
-
-       Distributed servers  : Distribution of servers will allow a number
-of significant benefits to be made available to all applications iusing the
-server:
-
-       Load balancing : When multiple servers are in use, operations can be
-spread over all available servers, to maximise system efficiency. Various
-resources (network access, memory, and CPU power for example) can be
-managed, with operations given to the most appropriate available server.
-
-       Fault tolerance : System failures can cause significant problems
-with computer systems. Fault tolerant systems rely on multiple servers
-running the same operation at one time as well as having multiple servers
-ready to take over. This means that serious failures can be handled
-automatically, without the user needing to be aware of the problem. Systems
-may be able to be automatically restarted, and administrators can be
-notified of the failure by the remaining systems.
-
-
-
-
-Directory structure:
-====================
-
-lib/      Contains modules that are either generally reusable, or used in more
-          than one GNUe program.
-
-src/      Contains the main GEAS server code. Each subdirectory contains a
-          single module.
-
-idl/      All IDL files used in GEAS
-
-doc/          All documentation
-doc/dia       Diagrams for GEAS
-doc/internals Internal details of GEAS: describes how GEA works
-doc/notes     Misc development notes - not updated on a regular basis, if ever.
-              General notes should be kept here by GEAS developers, describing
-               ideas and proposed algortihms to use
-
-tools/    Additional programs used in association with GEAS: will include
-          configuration assistants, class definition tools, and other
-          utilities for an active GEAS server.
-
-extra/    [ proposed ] Any custom utilities required to build GEAS will be
-          placed in this directory.
-
-examples/
-examples/businessobjects  Business objects used in the examples
-examples/python           Python based demo applications, using example
-                          business objects.
+The subdirectory 'doc' contains additional information. Since this is a
+development release, please don't expect all documentation to be 100% up
+to date.