/[gzz]/gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
ViewVC logotype

Diff of /gzz/Documentation/misc/hemppah-progradu/masterthesis.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.176 by hemppah, Mon Mar 24 11:44:58 2003 UTC revision 1.177 by hemppah, Mon Mar 24 12:31:59 2003 UTC
# Line 1591  which is an essential part of Fenfire's Line 1591  which is an essential part of Fenfire's
1591  \section{Overview}  \section{Overview}
1592    
1593  The Fenfire project \cite{fenfireurl} is an effort to build a location transparent, hyperstructured desktop  The Fenfire project \cite{fenfireurl} is an effort to build a location transparent, hyperstructured desktop
1594  environment. Fenfire uses xanalogical storage model \cite{ted-xu-model} as a basis for hyperstructured  environment. By location transparent, we mean concealing the heterogeneous and distributed nature of the system
1595  media. Fenfire deploys innovative user interfaces for displaying data to the end users. All data in the Fenfire  so that it appears to the end user like one system and by hyperstructured system,
1596  is stored in a unified format, i.e., blocks. This features should allow making references between \emph{any}  we mean a system in which data can be associated with other data arbitrarly. Fenfire uses xanalogical storage model
1597  data easier and more seamlessly interoperating than in other systems. For location transparency in a distributed system, Fenfire  \cite{ted-xu-model} as a basis for hyperstructured media. Each data item in the Fenfire system has a globally unique
1598  uses Peer-to-Peer network for locating and fetching blocks.  identifier. This property should allow making references between \emph{any}
1599    data easier and more seamlessly interoperating than in other systems. For location transparency in the Fenfire system,
1600  Fenfire is a free software and it is licensed under GNU LGPL.  Fenfire was formerly also a partial implementation  we are currently analysing the applicably of Peer-to-Peer infrastructure for locating and fetching blocks in a
1601    distributed environment. Fenfire was formerly also a partial implementation
1602  of the ZigZag\texttrademark -- structure, which has been originally invented  of the ZigZag\texttrademark -- structure, which has been originally invented
1603  by Ted Nelson. Now, however, Fenfire uses Resource Description Framework (RDF) \cite{w3rdfurl}  by Ted Nelson. Now, however, Fenfire uses Resource Description Framework (RDF) \cite{w3rdfurl}
1604  for representing internal data structures and their relationships.  for representing internal data structures and their relationships.
1605    
1606  Fenfire is a high modular software system. It consists of several independent software modules:  Fenfire is a free software and it is licensed under GNU LGPL. Moreover, Fenfire consists of several independent software modules:
1607    
1608  \begin{itemize}  \begin{itemize}
1609  \item \textbf{Storm}: a distributed storage module for storing arbitrary data items  \item \textbf{Storm}: a storage module for storing arbitrary data items
1610  \item \textbf{Navidoc}: an UML-based tool for generating software documentation    \item \textbf{Navidoc}: an UML-based tool for generating software documentation  
1611  \item \textbf{Alph}: a xanalogical hypertext built upon Storm storage model  \item \textbf{Alph}: a xanalogical hypertext built upon Storm storage model
1612  \item \textbf{GLMosaicText}: a flexible OpenGL interface for font manipulation  \item \textbf{GLMosaicText}: a flexible OpenGL interface for font manipulation
# Line 1613  Fenfire is a high modular software syste Line 1614  Fenfire is a high modular software syste
1614  \item \textbf{LibVob}: a graphic library used for creating navigation interfaces in complex data views  \item \textbf{LibVob}: a graphic library used for creating navigation interfaces in complex data views
1615  \end{itemize}  \end{itemize}
1616    
1617    In this thesis, we focus on Storm module as it is a foundation for Peer-to-Peer functionality
1618  For location transparency in the Fenfire system, Storm software module  in the Fenfire system.
 must have a support for Peer-to-Peer functionality as it provides low-level data storage operations  
 in the Fenfire system. Therefore, we focus on Storm and Alph modules, since they are the foundation of Fenfire's  
 Peer-to-Peer functionality. If not otherwise mentioned, we use term 'Storm' when referring to both  
 Storm and Alph software modules.  
   
1619    
1620  \section{Xanalogical storage model}  \section{Xanalogical storage model}
1621    

Legend:
Removed from v.1.176  
changed lines
  Added in v.1.177

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26