[JSPDBAdmin-cvs] CVS: jspdbadmin JSPDBADMIN-PROPOSAL.txt,1.1,1.2

[Adrian A. <aal...@us...>]

Update of /cvsroot/jspdbadmin/jspdbadmin
In directory usw-pr-cvs1:/tmp/cvs-serv19206

Modified Files:
	JSPDBADMIN-PROPOSAL.txt 
Log Message:
Some cosmetic changes to the proposal

Index: JSPDBADMIN-PROPOSAL.txt
===================================================================
RCS file: /cvsroot/jspdbadmin/jspdbadmin/JSPDBADMIN-PROPOSAL.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** JSPDBADMIN-PROPOSAL.txt	2 Sep 2002 23:34:40 -0000	1.1
--- JSPDBADMIN-PROPOSAL.txt	2 Sep 2002 23:50:53 -0000	1.2
***************
*** 1,4 ****
!                          Proposal for JSPDBAdmin
!                          =======================
  
  
--- 1,4 ----
!                        Proposal for JSPDBAdmin 1.0
!                        ===========================
  
  
***************
*** 11,28 ****
  - Create an API that can handle at least for starting ORACLE, MySQL Databases.
  - Provide maximum modularity in the API
! - - Make the core of the API just handling the most similar features of each DB.- Make a web interface that uses this API.
  - - This web interface must have i18n features.
  - - This web interface also have to cover all databases.
  - If we need to rely on a Servlet API we must use 2.3 for now
! - Also the servlet-container to use is the reference implementation for this Servlet API Tomcat 4.1.x
  
  
! Things TO DO:
! ============
! - Select the build tool we are going to use. (Jakarta-ant is the best proposed).- Select Logging, Database Pool, Taglibs we probably are going to need.
  
! Later:
! =====
! - After we have the core, then make extensions to every database specific
! features like DB File size, % of data occupied, and things like that.
  
--- 11,32 ----
  - Create an API that can handle at least for starting ORACLE, MySQL Databases.
  - Provide maximum modularity in the API
! - - Make the core of the API just handling the most similar features of each DB.
! - Make a web interface that uses this API.
  - - This web interface must have i18n features.
  - - This web interface also have to cover all databases.
  - If we need to rely on a Servlet API we must use 2.3 for now
! - Also the servlet-container to use is the reference implementation for this Servlet
!   API Tomcat 4.1.x
  
  
! Things TODO:
! ===========
! - Select the build tool we are going to use. (Jakarta-ant is the best proposed).
! - Select Logging, Database Pool, Taglibs we probably are going to need.
  
! 
! TODO Later:
! ==========
! - After we have the core, then make extensions to every database specific features 
!   like DB File size, % of data occupied, and things like that.