| Previous | Table of Contents | Next |
An implementation of an Interface Repository requires some form of persistent object store. Normally the kind of persistent
object store used determines how interface definitions are distributed and/or replicated throughout a network domain. For
example, if an Interface Repository is implemented using a filing system to provide object storage, there may be only a single
copy of a set of interfaces maintained on a single machine. Alternatively, if an OODB is used to provide object storage, multiple
copies of interface definitions may be maintained each of which is distributed across several machines to provide both high-availability
and load-balancing.
The kind of object store used may determine the scope of interface definitions provided by an implementation of the Interface
Repository. For example, it may determine whether each user has a local copy of a set of interfaces or if there is one copy
per community of users. The object store may also determine whether or not all clients of an interface set see exactly the
same set at any given point in time or whether latency in distributing copies of the set gives different users different views
of the set at any point in time.
An implementation of the Interface Repository is also dependent on the security mechanism in use. The security mechanism (usually
operating in conjunction with the object store) determines the nature and granularity of access controls available to constrain
access to objects in the repository.