--- nfo/perl/libs/Data/README.html	2002/11/29 04:48:23	1.4
+++ nfo/perl/libs/Data/README.html	2002/12/11 06:53:19	1.5
@@ -24,6 +24,13 @@
 
 	<LI><A HREF="#requirements">REQUIREMENTS</A></LI>
 	<LI><A HREF="#description">DESCRIPTION</A></LI>
+	<UL>
+
+		<LI><A HREF="#data::storage">Data::Storage</A></LI>
+		<LI><A HREF="#why">Why?</A></LI>
+		<LI><A HREF="#what else">What else?</A></LI>
+	</UL>
+
 	<LI><A HREF="#authors / copyright">AUTHORS / COPYRIGHT</A></LI>
 	<LI><A HREF="#acknowledgements">ACKNOWLEDGEMENTS</A></LI>
 	<LI><A HREF="#support / warranty">SUPPORT / WARRANTY</A></LI>
@@ -45,7 +52,8 @@
 <HR>
 <P>
 <H1><A NAME="name">NAME</A></H1>
-<P>Data::Storage - Interface for accessing various Storage implementations for Perl in an independent way</P>
+<PRE>
+  Data::Storage - Interface for accessing various Storage implementations for Perl in an independent way</PRE>
 <P>
 <HR>
 <H1><A NAME="aims">AIMS</A></H1>
@@ -167,8 +175,9 @@
   }</PRE>
 <P>
 <H2><A NAME="note">NOTE</A></H2>
-<P>This module heavily relies on DBI and Tangram, but adds a lot of additional bugs and quirks. 
-Please look at their documentation and/or this code for additional information.</P>
+<PRE>
+  This module heavily relies on DBI and Tangram, but adds a lot of additional bugs and quirks. 
+  Please look at their documentation and/or this code for additional information.</PRE>
 <P>
 <HR>
 <H1><A NAME="requirements">REQUIREMENTS</A></H1>
@@ -185,25 +194,48 @@
 <P>
 <HR>
 <H1><A NAME="description">DESCRIPTION</A></H1>
-<P>Data::Storage is a module for accessing various ``data structures'' stored inside
-various ``data containers''. It sits on top of DBI and/or Tangram.</P>
+<P>
+<H2><A NAME="data::storage">Data::Storage</A></H2>
+<PRE>
+  Data::Storage is a module for accessing various &quot;data structures / kinds of structured data&quot; stored inside
+  various &quot;data containers&quot;.
+  We tried to use the AdapterPattern (<A HREF="http://c2.com/cgi/wiki?AdapterPattern">http://c2.com/cgi/wiki?AdapterPattern</A>) to implement a wrapper-layer
+  around core CPAN modules (Tangram, DBI).</PRE>
+<P>
+<H2><A NAME="why">Why?</A></H2>
+<PRE>
+  You will get a better code-structure (not bad for later maintenance) in growing Perl code projects,
+  especially when using multiple database connections at the same time.
+  You will be able to switch between different _kinds_ of implementations used for storing data.
+  Your code will use the very same API to access these storage layers.
+      ... implementation has to be changed for now
+  Maybe you will be able to switch &quot;on-the-fly&quot; without changing any bits in code in the future.... 
+      ... but that's not the focus</PRE>
+<P>
+<H2><A NAME="what else">What else?</A></H2>
+<PRE>
+  Having this, we were able to do implement a generic data synchronization module more easy,
+  please look at Data::Transfer.</PRE>
 <P>
 <HR>
 <H1><A NAME="authors / copyright">AUTHORS / COPYRIGHT</A></H1>
-<P>The Data::Storage module is Copyright (c) 2002 Andreas Motl.
-All rights reserved.</P>
-<P>You may distribute it under the terms of either the GNU General Public
-License or the Artistic License, as specified in the Perl README file.</P>
+<PRE>
+  The Data::Storage module is Copyright (c) 2002 Andreas Motl.
+  All rights reserved.
+  You may distribute it under the terms of either the GNU General Public
+  License or the Artistic License, as specified in the Perl README file.</PRE>
 <P>
 <HR>
 <H1><A NAME="acknowledgements">ACKNOWLEDGEMENTS</A></H1>
-<P>Larry Wall for Perl, Tim Bunce for DBI, Jean-Louis Leroy for Tangram and Set::Object, 
-Sam Vilain for Class::Tangram, Jochen Wiedmann and Jeff Zucker for DBD::CSV and related,
-Adam Spiers for MySQL::Diff and all contributors.</P>
+<PRE>
+  Larry Wall for Perl, Tim Bunce for DBI, Jean-Louis Leroy for Tangram and Set::Object, 
+  Sam Vilain for Class::Tangram, Jochen Wiedmann and Jeff Zucker for DBD::CSV &amp; Co.,
+  Adam Spiers for MySQL::Diff and all contributors.</PRE>
 <P>
 <HR>
 <H1><A NAME="support / warranty">SUPPORT / WARRANTY</A></H1>
-<P>Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</P>
+<PRE>
+  Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</PRE>
 <P>
 <HR>
 <H1><A NAME="todo">TODO</A></H1>
@@ -271,7 +303,16 @@
     -  .wab - files (Windows Address Book)
     -  .pst - files (Outlook Post Storage?)
     -  XML (e.g. via XML::Simple?)
-  - Move to t3, look at InCASE</PRE>
+  - Move to t3, look at InCASE
+  - some kind of security layer for methods/objects
+    - acls (stored via tangram/ldap?) for functions, methods and objects (entity- &amp; data!?)
+    - where are the hooks needed then?
+      - is Data::Storage &amp; Co. okay, or do we have to touch the innards of DBI and/or Tangram?
+      - an attempt to start could be: 
+         - 'sub getACLByObjectId($id, $context)'
+         - 'sub getACLByMethodname($id, $context)'
+         - 'sub getACLByName($id, $context)'
+            ( would require a kinda registry to look up these very names pointing to arbitrary locations (code, data, ...) )</PRE>
 <P>
 <H3><A NAME="links / references">LINKS / REFERENCES</A></H3>
 <PRE>