[JSPDBAdmin-Developers] Getting started
Status: Planning
Brought to you by:
aalmenar
From: Andrew <an...@ne...> - 2001-10-22 20:31:15
|
Hi Adrian, All, On Sun, Oct 21, 2001 at 05:07:42PM -0400, Adrian Almenar quoth: > Hi Everyone, I have a sneaking suspicion this only came to me, just by looking at the headers. It seems the list's default action on 'reply' is to reply to the Author, not to the list. > Im thinking make a backend solution to work with a known Java Web Server > i.e. Apache-Tomcat. Yep. I like this, and I've done a little with Apache/Tomcat already, so it is a choice I'm comfortable with. This would be configured with the Client as a browser (anywhere), and the Gui and Backend code running on the Apache/ Tomcat server connecting to a Database (again theoretically anywhere). > Why ?, 'cause its easy to program and handle the UI and the DB connections > cause we dont want to saturate with connections a DB production Server. Yep. > im going to think better about how to implement a common framework and UI > for multiple Databases. Yeah... I don't think it should be that hard. The UI should be simple enough, we'd just need a section during initial login where Database type and location was entered (or as a config-file or option menu), as well as userid and password. I'm wondering if it will be feasible to leverage JDBC? Do all the target databases have JDBC driver support? If so then the backend won't even need to care about what sort of database it is talking to really. If not then we are getting into more proprietary db interaction methods, which will need to be tailored to each target db. A Wrapper Class for each such db would take the UI requests (for eg createTable(data)) and then pass the appropriately formatted request down the connection to the DBMS. > We can use Any authentication method to give privileges to access feature of > administration, but i think we should think about this later. Agreed... Cheers, Andrew. |