1 karl  1.1 /*
 2              Documentation on the various repositories contained in Pegasus

 3 karl  1.2 
 4           

 5 karl  1.1 */
 6           
 7           /** @name Repositories in Pegasus
 8           Pegasus allows the implementation of repositories through a standard
 9           repository interface as defined in another section of this document
10           \Ref{Repository Interfaces}.
11           
12           The Repository is an extension function of Pegasus. Both Class and instances
13           repositories are provider for.
14           
15           As delivered, the Pegasus code implements both a simple Class and instance
16           repository.  These repositories are not designed for speed or for very large
17           repositories. They are both implemented as directories and files on the
18           Pegasus host file system
19           
20           Developers of implementations of the Pegasus may chose to implement other
21           repositories (ex. datbase based repositories, remoted repositories, etc.) ath
22           their descretion.Another repository form can be implemented by creating a
23           handler for that repository using the Pegasus repository interface and
24           attaching that handler to Pegasus.
25           
26 karl  1.1 Today, that new repository must be added by replacing the existing repository
27           implementation module in Pegasus.  In the future Pegasus will allow for
28           additional or replacement repositories using the Pegasus extension modules.
29           
30           <B>Defintion of the Class Repository Implementation</B>
31           
32           ATTN: Not done
33           
34           <B>Defintion of the Instance Repository Implementation</B>
35           
36           ATTN: Not done
37           */