Abstract: Complex search tasks are performed relative to an LDAP directory with a minimal quantity of LDAP search operations. Search tasks that follow relationships between LDAP entries can be performed, even under circumstances in which those relationships are not represented by the hierarchical structure of the LDAP directory. A client application can specify an LDAP control that the client application sends to the LDAP server along with the LDAP search operation. The LDAP server's receipt of the LDAP control can cause the LDAP server to modify the behavior of the search operation so that the LDAP server follows potentially non-hierarchical specified relationships between the LDAP entries in determining the set of entries to return as results of the search operation. As a result, the LDAP server can return a complete set of related result entries to the client application in response to a single LDAP search operation directed by the application.

Abstract: Complex search tasks are performed relative to an LDAP directory with a minimal quantity of LDAP search operations. Search tasks that follow relationships between LDAP entries can be performed, even under circumstances in which those relationships are not represented by the hierarchical structure of the LDAP directory. A client application can specify an LDAP control that the client application sends to the LDAP server along with the LDAP search operation. The LDAP server's receipt of the LDAP control can cause the LDAP server to modify the behavior of the search operation so that the LDAP server follows potentially non-hierarchical specified relationships between the LDAP entries in determining the set of entries to return as results of the search operation. As a result, the LDAP server can return a complete set of related result entries to the client application in response to a single LDAP search operation directed by the application.

Abstract: A method for deploying a directory server that includes receiving a new version of the directory server on a server to replace a prior version of the directory server, wherein the new version of the directory server uses a new version of an access policy and the prior directory server uses a prior version of the access policy, and configuring the new version of the directory server to use both the prior version of access policy and the new version of the access policy, wherein the new version of the directory server maintains compatibility between the new version of the access policy and the prior version of the access policy.

Abstract: A method for managing access to a data element involves storing a first copy of the data element in a cache location, obtaining a request to modify the data element, where the request to modify the data element is associated with a first execution thread, marking the cache location as dirty based on the request to modify the data element, modifying the cache location according to the request to modify the data element once the cache location is marked as dirty, obtaining a request to read the data element while the cache location is marked as dirty, where the request to read the data element is associated with a second execution thread, providing a second copy of the data element in response to the request to read the data element based on the cache location being marked as dirty, and marking the cache location as clean after modifying the cache location is complete.

Abstract: A computer readable medium includes executable instructions for managing server configuration data by configuring a first server using local server configuration data, where the local server configuration data is stored on the first server and as shared server configuration data by a first directory service instance operating on the first server, synchronizing the first directory service instance with a second directory service instance operating on a second server, where the shared server configuration data is updated, and updating the local server configuration data using the updated shared server configuration data.

Abstract: A method for deploying a directory server that includes receiving a new version of the directory server on a server to replace a prior version of the directory server, wherein the new version of the directory server uses a new version of an access policy and the prior directory server uses a prior version of the access policy, and configuring the new version of the directory server to use both the prior version of access policy and the new version of the access policy, wherein the new version of the directory server maintains compatibility between the new version of the access policy and the prior version of the access policy.

Abstract: A computer readable medium includes executable instructions for managing server configuration data by configuring a first server using local server configuration data, where the local server configuration data is stored on the first server and as shared server configuration data by a first directory service instance operating on the first server, synchronizing the first directory service instance with a second directory service instance operating on a second server, where the shared server configuration data is updated, and updating the local server configuration data using the updated shared server configuration data.

Abstract: A method for managing access to a data element involves storing a first copy of the data element in a cache location, obtaining a request to modify the data element, where the request to modify the data element is associated with a first execution thread, marking the cache location as dirty based on the request to modify the data element, modifying the cache location according to the request to modify the data element once the cache location is marked as dirty, obtaining a request to read the data element while the cache location is marked as dirty, where the request to read the data element is associated with a second execution thread, providing a second copy of the data element in response to the request to read the data element based on the cache location being marked as dirty, and marking the cache location as clean after modifying the cache location is complete.

Abstract: The invention proposes a directory server, capable of interacting with entries organized in a tree structure. Each entry has attributes, these attributes comprising real attributes each having a value stored in the entry. The directory server comprising: a mechanism capable of associating a virtual attribute to an entry, subject to a virtual attribute condition being verified, the virtual attribute condition being derived from data located elsewhere in the tree structure, and a resolving function, capable of receiving a first filter expression, based on a virtual attribute, for converting it into one or more second filter expressions, containing real attributes, and being computed from the first filter expression and from the virtual attribute condition.

Abstract: A method of entry distribution includes receiving requests by a chaining backend from an original client, forwarding requests from the chaining backend to a one of a plurality of remote servers, and returning results from the one of the plurality of remote servers to the original client. The chaining backend is a type of database plug-in that acts as a multiplexer including a directory information tree that provides the hierarchy of the plurality of remote servers.

Abstract: A method of bulk import in a directory server, including defining an extended operation on a server and a client, sending an extended operation request from the client to the server, performing the extended operation after receiving the extended operation request from the server, sending a response of the server back to the client specifying an object identifier of the extended operation and data specific to the extended operation; and performing a series of LDAP add operations framed by extended operations to import an entry into the directory server. A bulk import system for a directory server, including a processor, a memory, extended operations defined on a server and a client, and software instructions residing in memory executable on the processor for performing a series of LDAP add operations framed by extended operations to import an entry into the directory server.

Abstract: The invention proposes a directory server, capable of interacting with entries organized in a tree structure. Each entry has attributes, these attributes comprising real attributes each having a value stored in the entry. The directory server comprising: a mechanism capable of associating a virtual attribute to an entry, subject to a virtual attribute condition being verified, the virtual attribute condition being derived from data located elsewhere in the tree structure, and a resolving function, capable of receiving a first filter expression, based on a virtual attribute, for converting it into one or more second filter expressions, containing real attributes, and being computed from the first filter expression and from the virtual attribute condition.

Abstract: A directory server including a supplier server, a consumer server in communication with the supplier server, a plurality of pluggable services that manage replication of data contained within the directory server from the supplier server to the consumer server, and a directory server mapping tree used to select a backend to handle a request. Replication of data is managed using the directory server mapping tree.

Abstract: A method to support access control checks in a directory server with a chaining backend includes binding a user to a multiplexer, forwarding an authentication sequence from the multiplexer to a first remote server, binding the user to the first remote server, authenticating the user if binding to the first remote server is successful, binding the multiplexer as a special user to a second remote server, where the second remote server holds target data, sending an operation and an original user identity from the user to the multiplexer, and forwarding the operation from the multiplexer to the second remote server.

Abstract: A method of bulk import in a directory server, including defining an extended operation on a server and a client, sending an extended operation request from the client to the server, performing the extended operation after receiving the extended operation request from the server, sending a response of the server back to the client specifying an object identifier of the extended operation and data specific to the extended operation; and performing a series of LDAP add operations framed by extended operations to import an entry into the directory server. A bulk import system for a directory server, including a processor, a memory, extended operations defined on a server and a client, and software instructions residing in memory executable on the processor for performing a series of LDAP add operations framed by extended operations to import an entry into the directory server.

Abstract: A method of entry distribution includes receiving requests by a chaining backend from an original client, forwarding requests from the chaining backend to a remote server, and returning results from the remote server to the original client. The chaining backend is a type of database plug-in that acts as a multiplexer with limited persistent storage capabilities.

Abstract: A mechanism for dispatching a sequence of packets via a telecommunications network includes a queue for packets for transmission and a queue controller responsive to receipt of a new packet for transmission to compare parameters of the new packet to parameters of any packet already in the queue, the queue controller determining whether to queue or drop the new packet depending on the result of the comparison(s). The queue can be implemented as a linked list of packet entries with individual pointers to the respective packets concerned. The queue entries can include details relating to the packet including data relating to the information flow and also the packet identity. In a TCP environment, the flow information can include the source IP address and the source TCP port, as well as the destination IP address and the destination TCP port. The identity information can include sequence numbers and acknowledgement numbers for the packet concerned.

Abstract: A dispatch mechanism is provided for dispatching data units, (e.g. datagrams or packets) divided into one or more fragments, via a telecommunications network. The dispatch mechanism includes a queue for queuing fragments for transmission. It further includes a queue controller operable when a fill level of the queue exceeds a threshold value to discard fragments of data units for which a fragment has not already been queued and to add to the queue fragments of data units for which a fragment has already been queued. The dispatch mechanism maintains a record of data units which are to be transmitted (that is when one fragment of the data unit has already been passed for despatch) and a record of data units which are to be dropped (that is data units for which a fragment has already been dropped). The dispatch mechanism enables more effective use of network capacity by reducing the possibility of incomplete data units being transmitted over the network.