ASP.NET HTTP runtime

• US 7,162,723 B2
• Filed: 06/29/2001
• Issued: 01/09/2007
• Est. Priority Date: 06/29/2001
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Guthrie, Scott D., Robsman, Dmitry
• Primary Examiner(s): Thomson; William
• Assistant Examiner(s): Ho; Andy
• Application Number:
  US09/894,828
• Publication Number:
  US 20030018827A1
• Time in Patent Office: 2,020 Days
• Field of Search: 719/318, 719/310, 719/316, 709/227, 709/230
• US Class Current: 719/318
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An HTTP request handling runtime includes a context object and an event pipeline for processing an HTTP request received at a host application from a client application. The context object logically represents the HTTP request and encapsulates at least one property associated with the received HTTP request. The context object is processed by the event pipeline, which includes a plurality of synchronous and/or asynchronous request events. A callback is generated when a request event is raised and when at least one application and/or module is registered with the request event. Each callback instantiates each application and module that is registered with the request event for processing the context object. The plurality of request events can include events that are in a deterministic order and/or request events that are in a non-deterministic order, such as an error event.

Claims

1. A Hypertext Transfer Protocol (HTTP) request handling runtime, comprising:

a context object logically representing an HTTP request that is received at a host application from a client application, the context object encapsulating at least one property associated with the received HTTP request;

an event pipeline corresponding to the context object, the event pipeline having a plurality of request events, each request event having a corresponding event and generating a call-back when the event corresponding to the request event is raised and when at least one of an application and a module is registered in association with the request event, each call-back initiating each application and each module that is registered in association with the request event to process the context; and

wherein the event pipeline is a separate instance of the event pipeline for each HTTP request that is received at the host application from a client application and wherein the separate instance of the event pipeline exists only during the lifetime of its corresponding context object.

2. The HTTP request handling runtime according to claim 1, wherein the plurality of request events have a deterministic order.

3. The HTTP request handling runtime according to claim 2, wherein at least one of the plurality of request events is a synchronous request event.

4. The HTTP request handling runtime according to claim 2, wherein at least one of the plurality of request events is an asynchronous request event.

5. The HTTP request handling runtime according to claim 2, wherein the plurality of request events further includes at least one request event having a non-deterministic order.

6. The HTTP request handling runtime according to claim 1, wherein the plurality of request events have a non-deterministic order.

7. The HTTP request handling runtime according to claim 6, wherein the plurality of non-deterministic order request events include an error event.

8. The HTTP request handling runtime according to claim 1, wherein a module is registered in association with a plurality of request events.

9. The HTTP request handling runtime according to claim 1, wherein HTTP request runtime parses the received HTTP request to form the context object that logically represents the HTTP request.

10. A method for processing a Hypertext Transfer Protocol (HTTP) request, comprising the steps of:

forming a context object that logically represents an HTTP request that is received at a host application from a client application, the context object encapsulating at least one property associated with the received request;

forming an event pipeline corresponding to the context object, the event pipeline having a plurality of request events, and each request event having a corresponding event;

generating a call-back when the event corresponding to a request event is raised and when at least one of an application and a module is registered in association with the request event;

initiating each application and each module that is registered in association with the request event in response to the callback for processing the context; and

wherein the step of forming the event pipeline corresponding to the context object forms the event pipeline as a separate instance for each HTTP request received at the host application from a client application and wherein the separate instance of the event pipeline exists only during the lifetime of its corresponding context object.

11. The method according to claim 10, further comprising a step of registering a module in association with at least one selected request event.

12. The method according to claim 10, further comprising a step of registering a plurality of modules in association with a selected request event.

13. The method according to claim 10, wherein the plurality of request events have a deterministic order.

14. The method according to claim 13, wherein at least one of the plurality of request events is a synchronous request event.

15. The method according to claim 13, wherein at least one of the plurality of request events is an asynchronous request event.

16. The method according to claim 15, wherein the plurality of request events further includes at least one request event having a non-deterministic order.

17. The method according to claim 10, wherein the plurality of request events have a non-deterministic order.

18. The method according to claim 17, wherein the plurality of non-deterministic order request events include an error event.

19. The method according to claim 10, wherein the step of forming the context object includes a step of parsing the received HTTP request to form the context object.

20. A computer-readable medium having computer-executable instructions for processing a Hypertext Transfer Protocol (HTTP) request comprising steps of:

forming a context object that logically represents an HTTP request that is received at a host application from a client application, the context object encapsulating at least one property associated with the received request;

forming an event pipeline corresponding to the context object, the event pipeline having a plurality of request events, and each request event having a corresponding event;

generating a call-back event when the event corresponding to a request event is raised and when at least one of an application and a module is registered in association with the request event;

initiating each application and each module that is registered in association with the request event in response to the callback for processing the context object; and

wherein the step of forming the event pipeline corresponding to the context object forms the event pipeline as a separate instance for each HTTP request received at the host application from a client application and wherein the separate instance of the event pipeline exists only during the lifetime of its corresponding context object.

21. The computer-readable medium according to claim 20, further comprising a step of registering a module in association with at least one selected request event.

22. The computer-readable medium according to claim 20, further comprising a step of registering a plurality of modules in association with a selected request event.

23. The computer-readable medium according to claim 20, wherein the plurality of request events have a deterministic order.

24. The computer-readable medium according to claim 20, wherein at least one of the plurality of request events is a synchronous request event.

25. The computer-readable medium according to claim 20, wherein at least one of the plurality of request events is an asynchronous request event.

26. The computer-readable medium according to claim 23, wherein the plurality of request events further includes at least one request event having a non-deterministic order.

27. The computer-readable medium according to claim 20, wherein the plurality of request events have a non-deterministic order.

28. The computer-readable medium according to claim 27, wherein the plurality of non-deterministic order request events include an error event.

29. The computer-readable medium according to claim 20, wherein the step of forming the context object includes a step of parsing the received HTTP request to form the context object.