Directory service for a computer network
1 Assignment
0 Petitions
Accused Products
Abstract
A distributed directory service for an on-line services network comprises multiple, separate services, referred to as “Directory Service Providers,” running on respective groups of application servers. Each Directory Service Provider stores and provides access to a respective hierarchical directory structure, with nodes of the directory structures representing the various on-line services and other content entities which may be accessed by end users of the network. Junction point nodes are used to provide user-transparent links between the different directory structures, so that the directory structures appear to end users as a single, hierarchical directory. A common application program interface (API) is implemented by all Directory Service Providers, allowing client applications running on computers of end users to access the different directory structures using a common set of software methods. Data items that are shared by multiple nodes, such as icon bitmaps and sound files, are optionally stored by the Directory Service Providers within a shared database (separately from the nodes), and are accessed via special API methods. Various forms of node filtering, including language-based filtering and access rights filtering, are performed by the Directory Service Providers to determine which nodes to show to end users.
-
Citations
54 Claims
-
1-49. -49. (Canceled)
-
50. In a computer network in which different users have different access rights with respect to different content entities, a method of providing users with a filtered directory of content entities, comprising the steps of:
-
(a) storing a plurality of content nodes within a hierarchical directory structure on at least one server, each of said content nodes comprising a respective list of properties, said content nodes representing and providing access to said content entities;
(b) receiving requests at said server for said content nodes, said requests generated on a client computer of a user of said network;
(c) for each content node requested in step (b), doing each of (i) determining whether said user is authorized to access said content node, and (ii) returning properties of said content node to said client computer if and only if said user is authorized to access said content node; and
(d) using said properties returned in step (c) to construct a filtered hierarchical directory structure on a screen of said client computer. - View Dependent Claims (51, 52, 53)
-
-
54-71. -71. (Canceled)
Specification