SYSTEMS AND METHODS FOR PROCESSING WEB SERVICE PIPED NETWORK REQUESTS

• US 20120331038A1
• Filed: 06/23/2011
• Published: 12/27/2012
• Est. Priority Date: 06/23/2011
• Status: Active Application

• Current Assignee: D2L Corporation
• Original Assignee: D2L Corporation
• Inventors: Yang, Lin
• Application Number:
  US13/167,686
• Publication Number:
  US 20120331038A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

The embodiments described herein relate to web service client/server systems. According to some embodiments, there is provided a web service system including at least one client processor adapted to generate and transmit at least one piped request comprising a plurality of discrete requests and at least one server processor in data communication with the client processor. The at least one server processor is adapted to receive the at least one piped request comprising the discrete requests, de-pipe each discrete request from the piped request and execute each discrete request to generate a result associated with the discrete request.

Claims

1. A web service system, comprising:

at least one client processor adapted to generate and transmit at least one piped request comprising a plurality of discrete requests;

at least one server processor in data communication with the client processor, the at least one server processor adapted to;

receive the at least one piped request comprising the discrete requests,

de-pipe each discrete request from the piped request; and

execute each discrete request to generate a result associated with the discrete request.

2. The system of claim 1, wherein the server processor is further adapted to generate and transmit at least one response to the one piped request based on at least one of the results generated.

3. The system of claim 2, wherein the server processor is adapted to provide a discrete request processing module operable to:

receive at least one of the discrete requests; and

execute the received discrete request to generate the result associated with that request.

4. The system of claim 3, wherein the server processor is adapted to provide a pipe controller module, and the discrete processing module is operable to:

receive the at least one piped request comprising the discrete requests;

de-pipe each discrete request from the piped request;

provide each discrete request to the discrete-request processing module; and

generate and transmit at least one response to the one piped request based on at least one of the results associated with the executed discrete requests.

5. The system of claim 4, wherein the pipe controller module is operable to generate a command associated with at least one of the discrete requests and provide the command to the discrete request processing module, and the discrete request processing module is operable to receive the command and execute the command to generate the result associated with that discrete request.

6. The system of claim 5, wherein the pipe controller module is adapted to generate the command based on at least one of the discrete requests and at least one of the results that has been previously generated by the discrete-request processing module.

7. The system of claim 1, wherein the at least one piped request is a web request for transmission over the Internet.

8. The system of claim 7, wherein the web request is compatible with hypertext transfer protocol (“

HTTP”

).

9. The system of claim 3, wherein the discrete request processor module is based on a model-view-controller (MVC) pattern for web applications based on ASP.NET framework.

10. The system of according to claim 4, wherein the discrete request processing module is operable to provide the generated result to the pipe controller module by storing the result in the data storage device at a particular location and the pipe controller module is operable to receive the result by referencing the result that is being stored at the particular location.

11. The web service system of claim 1, wherein the result generated by the discrete request processor module is a logical object.

12. The web service system of claim 1, wherein the discrete request processor module comprises a piped request handler sub-module for setting up an HTTP environment for processing the discrete request.

13. A web server comprising at least one server processor adapted to:

receive the at least one piped request comprising the discrete requests,

de-pipe each discrete request from the piped request; and

execute each discrete request to generate a result associated with the discrete request.

14. The server of claim 13, wherein the server processor is adapted to generate and transmit at least one response to the at least one piped request based on at least one of the results generated.

15. The server claim 13, wherein the server processor is adapted to provide a discrete request processing module, the discrete processing module being operable to:

receive at least one of the discrete request; and

execute the received discrete request to generate the result associated with that request.

16. The server of claim 14, wherein the server processor is further adapted to provide a pipe controller module operable to:

receive the at least one piped request comprising the discrete requests;

de-pipe each discrete request from the piped request;

provide each discrete request to the discrete-request processing module; and

generate and transmit at least one response to the one piped request based on at least one of the results associated with the executed discrete requests.

17. The server of claim 16, wherein the pipe controller module is operable to generate a command associated with at least one of the discrete request and provide the command to the discrete request processing module, and the discrete request processing module is operable to receive the command and execute the command to generate the result associated with that discrete request.

18. The server of claim 17, wherein the pipe controller module is adapted to generate the command based on at least one of the discrete requests and at least one of the results that has been previously generated by the discrete-request processing module.

19. The server of claim 13, wherein the at least one piped request is a web request for transmission over the Internet.

20. The server of claim 13, wherein the web request is compatible with hypertext transfer protocol (“

HTTP”

).

21. The server of claim 15, wherein the discrete request processor module is based on a model-view-controller (MVC) pattern for web applications based on ASP.NET framework.

22. The server of claim 16, wherein the discrete request processing module is operable to provide the generated result to the pipe controller module by storing the result in the data storage device at a particular location and the pipe controller module is operable to receive the result by referencing the result that is being stored at the particular location.

23. The server of claim 16, wherein the result generated by the discrete request processor module is a logical object.

24. The server of claim 16, wherein the discrete request processor module comprises a piped request handler sub-module for setting up an HTTP environment for processing the discrete request.

25. A computer-implemented web service method comprising:

receiving at least one piped request comprising a plurality of discrete requests;

de-piping each discrete request from the piped request; and

executing each discrete request to generate a result associated with the discrete request.

26. The method of claim 25 further comprising generating and transmitting at least one response to the one piped request based on at least one of the results generated.

27. The method of claim 25, wherein the step of de-piping each discrete request comprises generating a command associated with at least one of the discrete requests for execution.

28. The method of claim 25, wherein the step of generating the command comprises generating the command based on at least one of the discrete requests and at least one of the results generated by the discrete-request processing module.