home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.theory
- Path: sparky!uunet!digex.com!intercon!udel!bogus.sura.net!howland.reston.ans.net!usc!sdd.hp.com!saimiri.primate.wisc.edu!ames!decwrl!netcomsv!butch!iscnvx!news
- From: myoung@NEBULA.SSD.LMSC.LOCKHEED.COM
- Subject: Semantic Database
- Message-ID: <1993Jan27.170023.13608@iscnvx.lmsc.lockheed.com>
- Sender: news@iscnvx.lmsc.lockheed.com (News)
- Reply-To: myoung@NEBULA.SSD.LMSC.LOCKHEED.COM
- Organization: LMSC, Sunnyvale, California
- Date: Wed, 27 Jan 93 17:00:23 GMT
- Lines: 39
-
- Spanning Tree Semantics:
-
- Assume the user built a spanning tree, spanning say a collection
- of file directories across an enterprise. Now the user wished
- to perform text searches over all files spanned, or perform
- some file utility over the files, like back up for instance.
- How would the user define his semantics, and how would the user
- traverse the tree once built.
-
- Semantics of a Spanning Tree:
-
- span -> id (use the local node)
- or
- span -> move.span (move one or more steps)
-
- Files with unique filenames are identified as:
-
- span.file
-
- to guarantee move at least one hop away from the current node,
- and create a back up file name use:
-
- move.span.file_backup
-
- Using the wave syntax, the traversal of the spanning tree is accomplished
- with the following protocol:
-
- re(op($)) ! repeatedly traverse all outgoing paths.
-
- The re-entry rules would prevent endless broadcast.
-
- The user can use the spanning tree for regular file maintenance, or text
- searches. Any file, once placed on the spanning tree is accessible
- with the same semantic regardless of locations, assuming the name is unique.
- The spanning tree file system has disadvantages, and does not replace
- the traditional network file systems.
-
- The system requires that the semantic execution kernel exist in the
- intermediate nodes of the networks.
-