jon 01/08/06 14:28:59
Modified: . NOTES
Log:
minor fixes
added comments
Revision Changes Path
1.5 +13 -1 jakarta-turbine-torque/NOTES
Index: NOTES
===================================================================
RCS file: /home/cvs/jakarta-turbine-torque/NOTES,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- NOTES 2001/08/03 03:39:03 1.4
+++ NOTES 2001/08/06 21:28:59 1.5
@@ -14,7 +14,7 @@
that already use PoolMan, or the commons connection pool, or
the struts connection pool or whatever
-o XML an configuration
+o XML as configuration
o Use the digester to turn the datamodel into an object and
get rid of the dependency on xerces. It would be nice to
@@ -43,17 +43,27 @@
of data. typically there is no need to see a massive
set of records all at once.
+ [JSS] Not really database agnostic though. Must be implemented
+ conditionally.
+
o using proxies for large objects. if you had a user object
that had 50 attributes it would more efficient to create
a proxy object of that user that might have a few attributes,
enough to identify the object. you might use the proxy
objects in a list and when it is selected the real user
object is transparently retrieved.
+
+ [JSS] I consider this custom code and can be implemented in
+ the base objects quite easily.
o would it be possible to support native connection methods
for high efficiency. an easy to access C APIs, would it
even be useful?
+ [JSS] in this case, the JDBC driver can be made native and
+ is probably not a worry/optimization of ours because this
+ is handled in the JDBC layer.
+
o application programmers should be able to save, update, and
delete objects without any knowledge of the database schema.
if the attribute selection is based on columns in tables than
@@ -62,3 +72,5 @@
to change but you don't want this to affect application
programmers who may know little about databases. reasonably
so, the persistence layer should take care of everything.
+
+ [JSS] YES!
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
