Home   Info   DevZone   Wiki   UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
[ RegistryStructure ] [ not logged in ] [ Web: Imported ] goto:  options [ get info on or edit ] [ login or new user ] [ list of topics, hubs & nodes, or recent changes ]

RegistryStructure

See also: RegistryDesign

This file is to propose the basic structure of the proposed file: jos.registry.reg.xml, the system registry root-file

 * (root)
 |
 +- User
 |
 +- Handlers
 |	|
 |	+- Content
 |	|
 |	+- Protocol
 |
 +- Security
 |
 +- Components
 |
 +- Devices
 |
 +- Applications

User

User information; id est, name, password (encrypted), preferences, et al.

Handlers

Empty placeholder

HandlersContent

ContentHandlers

HandlersProtocol

ProtocolHandlers

Security

Securtiy information (hopefully secure itself ;) such as acl's and digital sigs. of users

Components

A list of properly installed JavaBeans (?)

Devices

All of the device drivers

Applications

All application specific registries are children of this

From each application node, there might be user-specific and host-specific settings. The user-specific settings should be available to the user even as they roam from one machine to another. A local registry should be able to import registry data from another machine on a network.

The host-specific settings are tied to a host, or machine. When a registry is integrated into a network, the list of different machines is shown by the network, like this:

* (root)

• hosts
  • host-1 (this)
    • user
      • user-1
        • app-1
        • app-2
        • app-3
      • user-2
        • app-1
      • user-3
        • app-3
    • application
      • app-1
      • app-2
      • app-3
  • host-2
    • user
      • user-1
        • app-1
        • app-2
        • app-3
      • user-2
        • app-1
      • user-3
        • app-3
    • application
      • app-1
      • app-2
      • app-3
  • host-3
    • user
      • user-1
        • app-1
        • app-2
        • app-3
      • user-2
        • app-1
      • user-3
        • app-3
    • application
      • app-1
      • app-2
      • app-3

In order to read/write any user profile, you must pass the security manager. You must be one of the users in the registry to gain access to this network. Any preferences one user might have compared to another must be imported into the user part of the registry. Since there are potentially different preferences for each application, these are arranged logically by application.

Each application should keep its original configuration and its default configuration. The default configuration is used each time a new user is added to the application. Parts of the application configuration are imported to the user node, for user preferences.

An application service on a network should store the application-specific configuration, instead of each machine.

Registry is a web of information. Each user has a set of applications. Each application has a set of users. Each host has a set of applications and a set of users.

GilbertHerschberger (26 May 1999)

Anyway, why not have network-wide registry that exists "on top" of the system registries it contains all the host info and also controls the transport of user and app sets between machines. This way on single user computers you dont have all that extra stuff "gunking it up".

DigiGod 99.05.26

• Dynamic nodes - Like you, I don't want dynamic information inside the registry. In RegistryDesign, it was proposed that device objects could be retrieved through a registry interface. The needs of the operating system devices and the registry are similar...but not the same. I think there should be a device interface for devices, a registry interface for registries.
• Objects - I have a problem with writing active objects into the registry. Imagine if a program could start a thread running, write it to the registry--because it's an object, too--and leave it running long after the application is gone. It would be (1) difficult to shutdown, and (2) difficult to make the registry secure. If, on the other hand, objects were serialized as they are written to the regisry, it doesn't address the point of storing active objects, like device drivers.

About a network-wide and system-wide registry. I am thinking that there should be two different registries. A system-wide registry should be provided for the system. A network-side registry should be provided for the network. For direct access to these registries, how about this:

Registry sr = SystemRegistry.getRegistry();
Registry nr = NetworkRegistry.getRegistry();

When using a registry URL, x-registry:os: returns a system-wide registry and x-registry:net: returns a network-wide registry.

GilbertHerschberger (4 June 1999)

Content of these pages are owned and copyrighted by the poster.
Hosted by: