PROVIDING ACCESS TO NETWORK APPLICATIONS FOR STANDARDIZED CLIENTS

• US 20090254670A1
• Filed: 04/08/2008
• Published: 10/08/2009
• Est. Priority Date: 04/08/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kim, Jacob, Jeyaseelan, Thomas, Bruno, John
• Application Number:
  US12/099,154
• Publication Number:
  US 20090254670A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A method for providing access to a network application for a standardized client. A hypertext transfer protocol (HTTP) request may be received from a standardized client. A resource request based on the HTTP request may be created. The resource request may be sent to the network application. A response may be received from the network application. A client response may be created based on the response. The client response may be sent to the standardized client.

Claims

1. A method for providing access to a network application, comprising:

a) receiving a hypertext transfer protocol (HTTP) request from a standardized client to access the network application;

b) creating a resource request based on the HTTP request;

c) sending the resource request to the network application;

d) receiving a response from the network application;

e) creating a client response based on the response; and

f) sending the client response to the standardized client.

2. The method of claim 1, wherein steps (a)-(f) are performed by an application programming interface (API) framework.

3. The method of claim 2, wherein the resource request is a representational state transfer (REST) request.

4. The method of claim 3, wherein the network application is a Web application.

5. The method of claim 1, further comprising encapsulating the HTTP request as an object within the resource request.

6. The method of claim 1, wherein the response includes a status message that indicates success or failure of the resource request.

7. The method of claim 1, wherein the client response is created based on a format of the standardized client.

8. The method of claim 7, wherein creating the client response comprises translating the response into the format of the standardized client.

9. The method of claim 8, wherein translating the response comprises:

serializing data within the response based on the format of the standardized client; and

including the serialized data in the client response.

10. The method of claim 7, wherein the format is one of really simple syndication (RSS), ATOM Syndication, JavaScript Object Notation, extensible markup language (XML), or binary XML.

11. The method of claim 7, wherein the HTTP request specifies the network application, an application resource associated with the network application, and the format of the standardized client.

12. The method of claim 11, further comprising restricting access to the application resource based on a policy of the network application.

13. A computer system, comprising:

a processor; and

a memory comprising an application programming interface (API) framework executable by the processor to;

receive a hypertext transfer protocol (HTTP) request from a standardized client;

create a REST request based on the HTTP request;

send the REST request to a Web application;

receive a response from the Web application;

create a client response based on the response and a format of the standardized client;

send the client response to the standardized client; and

translate the response into the format of the standardized client.

14. The computer system of claim 13, wherein the API framework executable by the processor to translate the response is further executable to:

serialize data within the response based on the format of the standardized client; and

include the serialized data in the client response.

15. A computer-readable medium having stored thereon computer-executable instructions which, when executed by a computer, cause the computer to:

receive a hypertext transfer protocol over secure socket layer (HTTPS) request from a standardized client for accessing a network application;

create a representational state transfer (REST) request based on the HTTPS request;

send the REST request to the network application;

receive a response from the network application;

create a client response based on the response; and

send the client response to the standardized client.

16. The computer-readable medium of claim 15, further comprising computer-executable instructions, which, when executed by a computer, cause the computer to encapsulate the HTTPS request as an object within the REST request.

17. The computer-readable medium of claim 15, wherein the computer-executable instructions that cause the computer to create the client response further cause the computer to create the client response based on a format of the standardized client.

18. The computer-readable medium of claim 17, wherein the computer-executable instructions that cause the computer to create the client response, further cause the computer to translate the response into the format of the standardized client.

19. The computer-readable medium of claim 18, wherein the computer-executable instructions that cause the computer to translate the response, further cause the computer to:

serialize data within the response based on the format of the standardized client; and

include the serialized data in the client response.

20. The computer-readable medium of claim 17, wherein the HTTPS request specifies the network application, an application resource associated with the network application, and the format of the standardized client.