Organizing resources into collections to facilitate more efficient and reliable resource access

• US 8,307,028 B2
• Filed: 09/09/2009
• Issued: 11/06/2012
• Est. Priority Date: 09/30/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kakivaya, Gopala Krishna R., Hasha, Richard L.
• Primary Examiner(s): Moise, Emmanuel L
• Assistant Examiner(s): KIM, EDWARD J
• Application Number:
  US12/556,399
• Publication Number:
  US 20100005071A1
• Time in Patent Office: 1,154 Days
• Field of Search: 709217-223, 709238-244, 709201-206, 709/245
• US Class Current: 709/201
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/3015 Name registration, generation or assignment
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

The present invention extends to methods, systems, and computer program products for organizing resources into collections to facilitate more efficient and reliable resource access. Namespace managers communicate with one another to form a federation namespace infrastructure. The infrastructure can efficiently route, migrate, and process namespace requests, such as, for example, namespace registration requests from providers requesting to manage portions of namespaces and lookup requests from consumers requesting access to managed resources. Resources can be registered in and made accessible from multiple different namespaces. Resources can be identified using nested queries that filter results at multiple levels of a hierarchical namespace.

Claims

1. At a computer system including one or more processors and system memory, a method for routing a namespace registration request from a resource provider providing a resource to an appropriate namespace manager that manages a namespace branch corresponding to the resource, the method comprising:

an act of a particular namespace manager receiving a namespace registration request from a resource provider to register a resource as a namespace branch within a namespace tree,

the namespace tree defining an arrangement of available resources via a plurality of namespace branches, each namespace branch being associated with at least one corresponding namespace manager,

the namespace registration request including a namespace identifier that identifies the resource within one of the plurality of namespace branches, the namespace identifier comprising a scheme portion that identifies a scheme type of the namespace identifier and a path portion identifying a path to the resource within the namespace tree;

the particular namespace manager being included in a plurality of namespace managers that have formed federating relationships with one another to exchange namespace information, each namespace manager assigned a unique numeric identifier;

an act of the particular namespace manager generating an at least one-way equivalent numeric identification value for the resource based on the namespace identifier, including generating the at least one-way equivalent numeric identification value based on a combination of at least the scheme portion of the namespace identifier along with at least one part of the path portion of the namespace identifier;

an act of the particular namespace manager sending the namespace registration request to a destination namespace manager having an identifier that is numerically closer to the at least one-way equivalent numeric identification value than other identifiers of other namespace managers in the plurality of namespace managers; and

an act of associating the destination namespace manager with the namespace branch.

2. The method as recited in claim 1, wherein the destination namespace manager floods the namespace registration request among a plurality of namespace managers within a neighborhood set of the destination namespace manager, the neighborhood set being a set of namespace managers having identifiers within a predefined range on either side of the identifier of the destination namespace manager within a finite modulo ID-address-space.

3. The method as recited in claim 1, further comprising an act of canonicalizing the namespace identifier per rules identified by the scheme portion of the namespace identifier before transferring the registration request over the namespace federation infrastructure.

4. The method as recited in claim 1, wherein the at least one-way equivalent numeric identification value that is based on a combination of at least the scheme portion of the namespace identifier along with at least one part of the path portion of the namespace identifier comprises a hash value.

5. The method as recited in claim 4, wherein the hash value for the namespace identifier varies based on the configuration of the namespace federation infrastructure.

6. The method as recited in claim 1, further comprising generating a hash over the entire namespace.

7. The method as recited in claim 4, wherein, for authoritative namespaces indicated by a “

;

//”

character sequence, the hash value is generated over the scheme portion, the “

;

//”

character sequence, an authority portion, and the path portion of the namespace identifier.

8. The method as recited in claim 4, wherein, for non-authoritative namespaces indicated by a “

;

/”

character sequence, the hash value is generated over the scheme portion, the “

;

/”

character sequence, and the path portion of the namespace identifier.

9. The method as recited in claim 4, further comprising utilizing one or more federation protocols to forward the hash value along with the namespace registration request to an appropriate namespace manager.

10. The method of claim 9, further comprising:

an act of receiving an indication that the appropriate namespace manager that received the forwarded hash and namespace registration request has migrated responsibility for the namespace branch to an other namespace manager, wherein the indication includes a referral to the other namespace manager that has responsibility for the namespace branch; and

an act of forwarding the hash and namespace registration request to the other namespace manager based on the referral.

11. The method of claim 1, further comprising:

an act of determining that an association between the destination namespace manager and the namespace branch is broken due to at least one of a namespace manager failure or the receiving of a referral to a different namespace manager; and

an act of routing subsequent requests until a new association is formed.

14. The method as recited in claim 1, wherein the act of generating the at least one-way equivalent numeric identification value comprises generating a hash over the scheme portion of the namespace identifier, at least a “

;

”

character, and at least one part of the path portion of the namespace identifier.

15. The method as recited in claim 1, wherein the scheme portion of the namespace identifier includes a namespace type of the namespace tree, and wherein the act of generating an at least one-way equivalent numeric identification value for the resource based on the namespace identifier of the namespace lookup request comprises an act of generating a hash over the namespace type.

12. One or more computer storage devices having stored thereon computer executable instructions that, when executed by one or more processors of a computer system, implement a method for routing a namespace registration request from a resource provider providing a resource to an appropriate namespace manager that manages a namespace branch corresponding to the resource, the method comprising:

a particular namespace manager receiving a namespace registration request from a resource provider to register a resource as a namespace branch within a namespace tree,

the namespace tree defining an arrangement of available resources via a plurality of namespace branches, each namespace branch being associated with at least one namespace manager,

the namespace registration request including a namespace identifier that identifies the resource within one of the plurality of namespace branches, the namespace identifier comprising a scheme portion that identifies a scheme type of the namespace identifier and a path portion identifying a path to the resource within the namespace tree;

the particular namespace manager calculating an at least one-way equivalent numeric identification value for the resource based on the namespace identifier, including calculating the at least one-way equivalent identification value based on a combination of at least the scheme portion of the namespace identifier along with at least one part of the path portion of the namespace identifier;

the particular namespace manager forwarding the namespace registration request to a destination namespace manager having an identifier that is numerically closer to the at least one-way equivalent numeric identification value than other identifiers of other namespace managers; and

associating the destination namespace manager with the namespace branch.

13. A computer system, comprising:

one or more processors; and

one or more computer storage devices storing executable instructions that, when executed by the one or more processors, implement a method for routing a namespace registration request from a resource provider providing a resource to an appropriate destination namespace manager that manages a namespace branch corresponding to the resource, the method comprising;

receiving a namespace registration request from a resource provider to register a resource as a namespace branch within a namespace tree, the namespace tree defining an arrangement of available resources via a plurality of namespace branches, each namespace branch being associated with at least one namespace manager, the namespace registration request including a namespace identifier that identifies the resource within one of the plurality of namespace branches, the namespace identifier comprising a scheme portion that identifies a scheme type of the namespace identifier and a path portion identifying a path to the resource within the namespace tree;

computing an at least one-way equivalent numeric identification value for the resource based on the namespace identifier, including computing the at least one-way equivalent identification value based on a combination of at least the scheme portion of the namespace identifier along with at least one part of the path portion of the namespace identifier;

sending the namespace registration request to a destination namespace manager having an identifier that is numerically closer to the at least one-way equivalent numeric identification value than other identifiers of other namespace managers; and

associating the destination namespace manager with the namespace branch.