Method and system for improving write performance in a supplemental directory

• US 20070112877A1
• Filed: 11/09/2005
• Published: 05/17/2007
• Est. Priority Date: 11/09/2005
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Harvey, Richard, Ramsay, Ronald, McDonald, Justin
• Granted Patent: US 8,326,899 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping

Abstract

According to one embodiment, a method of processing an update operation in a directory system having a reference layer having directory functionality and a supplemental layer operative intermediate the reference layer and a user is provided. The supplemental layer comprises a non-persistent store. The method includes receiving the update operation the update operation having an associated attribute and determining whether the attribute associated with the update operation is stored in the non-persistent store.

Claims

1-36. -36. (canceled)

37. A method of processing an update operation in a directory system having a reference layer having directory functionality and a supplemental layer operative intermediate the reference layer and a user, wherein the supplemental layer comprises a non-persistent store, the method comprising:

receiving the update operation, the update operation having an associated attribute; and

determining whether the attribute associated with the update operation is stored in the non-persistent store.

38. The method of claim 37, and further comprising determining whether the attribute associated with the update operation is stored in the directory system only in the non-persistent store.

39. The method of claim 37, and further comprising determining whether the attribute associated with the update operation is stored in a non-persistent store associated with a peer directory.

40. The method of claim 37, and further comprising determining whether the attribute associated with the update operation is stored in a persistent store associated with either the supplemental layer or the reference layer.

41. The method of claim 37, and further comprising determining whether the attribute associated with the update operation is stored in a non-persistent store associated with the peer directory and determining whether the attribute associated with the update operation is stored in a persistent store associated with either the supplemental layer or the reference layer.

42. A method of processing an update operation in a directory system having a reference layer having directory functionality and a supplemental layer operative intermediate reference layer and a user, wherein the supplemental layer comprises a non-persistent store, the method comprising:

receiving the update operation, the update operation having an associated attribute; and

determining whether the attribute associated with the update operation has an attribute type of permanent, persistent, or temporary.

43. The method of claim 42, wherein:

a permanent attribute type is stored in a persistent store associated with the reference layer or a persistent store associated with the supplemental layer;

a persistent attribute type is stored in at least a non-persistent store associated with the supplemental layer or a non-persistent store associated with a peer directory in the directory system; and

a temporary attribute type is stored in the directory system only in a non-persistent store associated with the supplemental layer.

44. The method of claim 42, and further comprising performing the update operation based on whether the attribute type is a permanent, persistent, or temporary.

45. The method of claim 44, wherein performing the update operation comprises writing to a permanent store if the attribute type is permanent.

46. The method of claim 45, wherein writing to a permanent store comprises writing to disk.

47. The method of claim 42, and further comprising performing the update operation by chaining the operation to the peer directory if the attribute type is persistent.

48. The method of claim 42, and further comprising performing the update operation if the attribute type is persistent.

49. The method of claim 42, and further comprising performing the update operation by writing to a directory having non-persistent storage if the attribute type is persistent.

50. The method of claim 42, and further comprising performing the update operation by writing to a directory to a non-persistent store if the attribute type is temporary.

51. The method of claim 42, wherein the update operation is selected from the group consisting of a modify-entry, a modify-DN, an add-entry, and a remove-entry.

52. The method of claim 42, wherein determining whether the attribute associated with the update operation has an attribute type of permanent, persistent, or temporary comprises determining one or more of the following:

an attribute type of a directory, a value of an attribute type, and whether a user of the directory system is selected.

53. The method of claim 42, and further comprising updating the attributes in a non-persistent information store.

54. A supplemental directory adapted to provide supplemental directory functionality in association with a reference directory having directory functionality, the supplemental directory operative intermediate the reference directory and a user, wherein the supplemental directory further comprises a non-persistent store for use in evaluating queries, wherein the supplemental directory is operable to receive an update operation associated with an attribute and further operable to:

determine whether the attribute associated with the update operation has an attribute type of permanent, persistent, or temporary.

55. A directory of claim 54 wherein:

a permanent attribute type is stored in a persistent store associated with the reference directory or a persistent store associated with the supplemental directory;

a persistent attribute type is stored in at least a non-persistent store associated with the supplemental directory and a non-persistent store associated with a peer directory; and

a temporary attribute is stored only in a non-persistent store associated with the supplemental directory.

56. The system of claim 54, wherein the supplemental directory is further operable to perform the update operation based on whether the attribute type is permanent, persistent, or temporary.

57. The supplemental directory of claim 56, wherein the supplemental directory is operable to perform the update operation by writing to a permanent store if the attribute type is permanent.

58. The supplemental directory of claim 57, wherein writing to a permanent store comprises writing to disk.

59. The supplemental directory of claim 54, wherein the supplemental directory is operable to perform the update operation by chaining the operation to a peer directory if the attribute type is persistent.

60. The supplemental directory of claim 54, wherein the supplemental directory is operable to perform the update operation if the attribute type is persistent.

61. The supplemental directory of claim 54, wherein the supplemental directory is further operable to perform the update operation by writing to a directory having non-persistent storage if the attribute type is persistent.

62. The supplemental directory of claim 54, wherein the supplemental directory is further operable to perform the update operation by writing to a non-persistent store if the attribute type is temporary.

63. The supplemental directory of claim 54, wherein the update operation is selected from the group consisting of a modify-entry, a modify-DN, an add-entry, and a remove-entry.

64. The supplemental directory of claim 54, wherein the supplemental directory is further operable to determine whether the attribute associated with the update operation has an attribute type of permanent, persistent, or temporary by determining one or more of the following:

an attribute type of a directory, a value of an attribute type, and whether the user of the supplemental directory is selected.

65. The supplemental directory of claim 54, wherein the supplemental directory is further operable to update the attribute in a non-persistent information store.

66. A directory system comprising a supplemental directory having supplemental directory functionality and a reference directory having directory functionality, the supplemental directory operative intermediate the reference layer and a user, the supplemental directory comprising a non-persistent information store for use in evaluating queries, and wherein the supplemental directory is further operable to:

determine whether an attribute associated with an update operation has an attribute type of permanent, persistent, or temporary;

wherein a permanent attribute type is stored in a persistent store associated with a reference layer or a persistent store associated with the supplemental layer;

wherein a persistent attribute type is stored in at least a non-persistent store associated with the supplemental directory and a non-persistent store associated with a peer directory; and

wherein a temporary attribute is stored only in a non-persistent store associated with a supplemental directory.

67. The directory system of claim 66, wherein the supplemental directory is further operable to perform the update operation based on whether the attribute type is permanent, persistent, or temporary.

68. The directory system of claim 67, wherein the supplemental directory is operable to perform the update operation by writing to a permanent store if the attribute type is permanent.

69. The directory system of claim 67, wherein the supplemental directory is operable to perform the update operation if the attribute type is permanent.

70. The directory system of claim 68, wherein writing to a permanent store comprises writing to disk.

72. The directory system of claim 66, wherein the supplemental directory is further operable to perform the update operation by writing to a directory having non-persistent storage if the attribute type is persistent.

73. The directory system of claim 66, wherein the supplemental directory is further operable to perform the update operation by writing to a non-persistent store if the attribute type is temporary.

74. The directory system of claim 66, wherein the update operation is selected from the group consisting of a modify-entry, a modify-DN, an add-entry, and a remove-entry.

75. The directory system of claim 66, wherein the supplemental directory is further operable to determine whether the attribute associated with the update operation has an attribute type of permanent, persistent, or temporary by determining one or more of the following:

an attribute type of a directory, a value of an attribute type, and whether the user of the supplemental directory is selected.

76. The directory system of claim 66, wherein the supplemental directory is further operable to update the attribute in a non-persistent information store.

77. The directory system of claim 66, wherein the update operation comprises an operation defined in a standard selected from the group consisting of X.500, LDAP, and DSML.

78-154. -154. (canceled)