Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for invoking execution of a plug-in that is dynamically bound to a database operation, comprising: receiving, at a database directory server, a first request from a client to perform a database operation, wherein the first request includes a first directory-access control message which is specific to the request and specifies a first plug-in chosen by a user; binding the first plug-in to the database operation so that the first plug-in is executed before, after, or during execution of the database operation; receiving a second request to perform the database operation, wherein the second request includes a second directory-access control message which specifies a second plug-in; and binding the second plug-in to the database operation so that the second plug-in is executed before, after, or during execution of the database operation.
2. The method of claim 1 , wherein the first or the second request to perform the database operation includes context-information associated with the operation.
3. The method of claim 2 , wherein executing a plug-in involves sending the context-information to a plug-in server to facilitate executing the plug-in.
4. The method of claim 2 , wherein the context-information can include: an operation-identifier; a set of operation-arguments; and a user-identifier.
5. The method of claim 1 , wherein the first or the second request to perform the database operation can include a time-specification which specifies when to execute the plug-in.
6. The method of claim 1 , wherein the first or the second directory-access control message includes a plug-in list which specifies a list of plug-ins to execute.
7. The method of claim 1 , wherein executing a plug-in involves: determining if a set of invocation-criteria associated with the plug-in has been satisfied; if so, executing the plug-in; and if not, sending an error message to the client.
8. The method of claim 7 , wherein the set of invocation-criteria can include: an existence-value which specifies whether the plug-in exists; a data-context which specifies what data the plug-in can access; a valid-group identifier which specifies which users can request that the plug-in be executed; an invalid-group identifier which specifies which users cannot request that the plug-in be executed; and a user-specified invocation-criteria.
9. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for invoking the execution of a plug-in that is dynamically bound to a database operation, the method comprising: receiving, at a database directory server, a first request from a client to perform a database operation, wherein the first request includes a first directory-access control message which is specific to the request and specifies a first plug-in chosen by a user; binding the first plug-in to the database operation so that the first plug-in is executed before, after, or during execution of the database operation; receiving a second request to perform the database operation, wherein the second request includes a second directory-access control message which specifies a second plug-in; and binding the second plug-in to the database operation so that the second plug-in is executed before, after, or during execution of the database operation.
10. The non-transitory computer-readable storage medium of claim 9 , wherein the first or the second request to perform the database operation includes context-information associated with the operation.
11. The non-transitory computer-readable storage medium of claim 10 , wherein executing a plug-in involves sending the context-information to a plug-in server to facilitate executing the plug-in.
12. The non-transitory computer-readable storage medium of claim 10 , wherein the context-information can include: an operation-identifier; a set of operation-arguments; and a user-identifier.
13. The non-transitory computer-readable storage medium of claim 9 , wherein the first or the second request to perform the operation can include a time-specification which specifies when to execute the first or the second plug-in.
14. The non-transitory computer-readable storage medium of claim 10 , wherein the first or the second directory-access control message includes a plug-in list which specifies a list of plug-ins to execute.
15. The non-transitory computer-readable storage medium of claim 9 , wherein executing a plug-in involves: determining if a set of invocation-criteria associated with the plug-in has been satisfied; if so, executing the plug-in; and if not, sending an error message to the client.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the set of invocation-criteria can include: an existence-value which specifies whether the plug-in exists; a data-context which specifies what data the plug-in can access; a valid-group identifier which specifies which users can request that the plug-in be executed; an invalid-group identifier which specifies which users cannot request that the plug-in be executed; and a user-specified invocation-criteria.
17. An apparatus that invokes the execution of a plug-in that is dynamically bound to a database operation, comprising: a processor; a receiving mechanism coupled to the processor to receive a first request from a client to perform a database operation, wherein the first request includes a first directory-access control message which is specific to the request and specifies a first plug-in chosen by a user; and a binding mechanism configured to bind the first plug-in to the database operation so that the first plug-in is executed before, after, or during execution of the database operation; wherein the receiving mechanism is further configured to receive a second request to perform the database operation, wherein the second request includes a second directory-access control message which specifies a second plug-in; and wherein, in response to receiving the second request, the binding mechanism is further configured to bind the second plug-in to the database operation so that the second plug-in is executed before, after, or during execution of the database operation.
18. The apparatus of claim 17 , further comprising a sending mechanism configured to send context-information to a plug-in server to facilitate executing a plug-in.
19. The apparatus of claim 17 , further comprising a determination mechanism configured to determine if a set of invocation-criteria associated with a plug-in has been satisfied.
20. The apparatus of claim 17 , wherein the apparatus is part of a directory server.
Unknown
November 19, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.