
=   AlexisDoc  >  Programming  > Client Server > RELATIONAL FILESYTEMS AND xml repositories


 SOME LINKS

   http://www.halfbakery.com/idea/Relational_20DB_20OS

   http://www.thinkgeek.com/stuff/looflirpa/wil.shtml

   To  some  extent,  an  XML "model" repository is a crippled relational
   filesystem:  it  stores the atoms (document nodes) and their hierarchy
   (DOM  tree) in separate tables, with implementation-specific levels of
   indexing   (/caching)   to  speed  document  retreival.  A  relational
   filesystem,  even  if  (as  is  planned  for  the moment) treating XML
   documents  at  the  document  rather than element level, can be easily
   extended to cover this functionality...in fact the idea of a collation
   document is a [more flexible] implementation of an XML repository.

   The  idea  of  file  is  simply an agreed upon contract, or interface,
   whereby  communication  can  occur.  What  happens  on the server with
   respect  to  storage and locking (and in a client editing environment)
   is  obviously file-type specific, but a lot of the infrastructure of a
   relational  filesystem  would  map  naturally  to a finer substructure
   policy.

 TO DO
 
     * Client:  Netbeans multi-file object?? Mappings (probably better to
       have doc-specific, but poss. extending)
     * Server:  Make  sure  the  interfaces to "file" are uncluttered, to
       allow easy later substitution.

   
