Application programming interface for implementing directory service access using directory service markup language

• US 20040243668A1
• Filed: 05/30/2003
• Published: 12/02/2004
• Est. Priority Date: 05/30/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Harjanto, Andy
• Granted Patent: US 7,668,902 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A set of DSML application programming interface (DSML API) functions is provided to facilitate the implementation of DSML-based directory service access. The DSML API includes a DSML document API class for building or accessing a DSML payload, and a DSML connection API class that handles connection and transport to a DSML server. To access a directory service, the client calls functions of the DSML document API class to generate a DSML request payload, and calls functions of the DSML connection API to transport a packet with the DSML request payload according to a pre-selected connection protocol, such as SOAP, to the DSML server for forwarding to the directory service.

Claims

1. A computer-readable medium having computer-executable instructions for performing steps for accessing a directory service, comprising:

calling a first API function defined in a document API class to construct a DSML request; and

calling a second API function defined in a connection API class to send a request packet having the DSML request as a payload under a networking protocol.

2. A computer-readable medium as in claim 1, wherein the networking protocol includes SOAP.

3. A computer-readable medium as in claim 2, wherein the request packet is sent using SOAP over HTTP.

4. A computer-readable medium as in claim 2, wherein the request packet is sent using SOAP over DIME.

5. A computer-readable medium as in claim 1, wherein the request packet is sent over a FILE binding.

6. A computer-readable medium as in claim 1, wherein the request packet is sent to a DSML server for forwarding to the directory service.

7. A computer-readable medium as in claim 1, having further computer-executable instructions for performing steps of:

receiving a response packet having a DSML response as a payload;

calling a third API function of the document API class to process the DSML response.

8. A computer-readable medium as in claim 1, wherein the document API class and the connection API class are separate and independent from each other.

9. A method of accessing a directory service, comprising:

calling a first API function defined in a document API class to construct a DSML request;

calling a second API function defined in a connection API class to send a request packet having the DSML request as a payload under a networking protocol.

10. A method as in claim 9, wherein the networking protocol includes SOAP.

11. A method as in claim 10, wherein the request packet is sent using SOAP over HTTP.

12. A method as in claim 10, wherein the request packet is sent using SOAP over DIME.

13. A method as in claim 9, wherein the request packet is sent over a FILE binding.

14. A method as in claim 9, wherein the request packet is sent to a DSML server for forwarding to the directory service.

15. A method as in claim 9, having further computer-executable instructions for performing steps of:

receiving a response packet having a DSML response as a payload;

calling a third API function of the document API class to process the DSML response.

16. A method as in claim 9, wherein the document API class and the connection API class are separate and independent from each other.

17. A computer-readable medium having computer-executable instructions for performing API functions for accessing a directory service using DSML, comprising:

a first group of API functions defined by a document API class for building a DSML request and processing a DSML response;

a second group of API functions defined by a connection API class, including functions for sending a request packet having the DSML request as a payload under a transport protocol,

wherein the document API class and connection API class are separate and independent from each other.

18. A computer-readable medium as in claim 17, wherein the networking protocol includes SOAP.

19. A computer-readable medium as in claim 17, wherein the request packet is sent using SOAP over HTTP.

20. A computer-readable medium as in claim 17, wherein the request packet is sent to a DSML server for forwarding to the directory service.