Client-side callbacks to server events

• US 20050256933A1
• Filed: 05/07/2004
• Published: 11/17/2005
• Est. Priority Date: 05/07/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Millington, Bradley D., Lin, Andrew Cheng-Min, Kothari, Nikhil
• Granted Patent: US 7,890,604 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems and methods for client-side callbacks to server events are described. In one aspect, a Web server receives a message indicating a client-side event. The client-side event is associated with a specific component of a client resource. The specific component is one of multiple static components of the client resource. A server-side component generates a response to the message. The server-side component implements at least a subset of logic of the specific component. Server-side logic corresponding to other ones of the static components that are different than the specific component is not used to generate the response.

Claims

1. A method comprising:

receiving, by a Web server, a message indicating a client-side event associated with a specific component of a client resource, the specific component being one of multiple static components of the client resource; and

generating, by a server-side component, a response to the message, the server-side component implementing at least a subset of logic of the specific component, server-side logic corresponding to other ones of the static components not being used to generate the response.

2. A method as recited in claim 1, wherein the static components comprise a form.

3. A method as recited in claim 1, and wherein at least a subset of the static components are being presented to a user by a browser-based Web application executing on a client computing device.

4. A method as recited in claim 1, wherein server-side logic for the static components is identified with a Universal Resource Identifier (URI)

5. A method as recited in claim 1, wherein the response is not a full page postback.

6. A method as recited in claim 1, wherein the response does not comprise rendered markup language.

7. A method as recited in claim 1, wherein the response is an incremental update of the client resource, the incremental update not being directed to update of respective ones of the static components different from the specific component.

8. A method as recited in claim 1, and further comprising communicating, by the server-side component, the response to a client side callback handler specified by the specified server-side component.

9. A method as recited in claim 1, and further comprising the server-side component identifying a client-side event handler to receive the response in view of an error.

10. A method as recited in claim 1, wherein the client resource is a page, and wherein generating the response further comprises not performing a full page lifecycle for the page.

11. A method as recited in claim 10, wherein not performing a full page lifecycle for the page comprises not pre-rendering or rendering information associated with any one of the static components different from the specific component.

12. A method as recited in claim 10, wherein not performing a full page lifecycle for the page comprises not pre-rendering or rendering information associated with the specific component.

13. A method comprising:

communicating, by a client device, a message to a targeted subset of server-side logic embedded in a Universal Resource Identifier (URI), the message identifying an event associated with at least one specific component of a resource being hosted by the client device, the resource comprising a plurality of static components that include the at least one specific component; and

receiving by the client device, a response to the message from a Web server, the response being generated by a server-side component that logically corresponds to the at least one specific component, the response not comprising data generated by any server-side control associated with respective ones of the static components different than the specific control.

14. A method as recited in claim 13, wherein the static components comprise a Web page.

15. A method as recited in claim 13, wherein the response does not comprise a rendering of a markup language.

16. A method as recited in claim 13, wherein the response is not a full page postback.

17. A method as recited in claim 13, and further comprising presenting, by a browser-based Web application executing at the client device, at least a subset of the static components.

18. A method as recited in claim 13, and further comprising, responsive to receiving the response, incrementally updating only portion(s) of the resource corresponding to the at least one specific component.

19. A method as recited in claim 13, and further comprising, responsive to receiving the response, rendering data in the response into a markup language for presentation on a display device, the data only corresponding to the at least one specific component.

20. A method as recited in claim 13, and further comprising, providing interactivity, by a Web application executing on the client device and hosting the resource, to a user during a time period from the communicating to the receiving, the interactivity being provided with respect to at least a subset of the static components that are different than the at least one specific component.

21. A computer-readable medium comprising computer-executable instructions for client-side callbacks to server events, the computer-executable instructions comprising instructions for:

receiving, by server-side logic embedded in a URI, a message indicating an event associated with a specific component of a client resource, the specific component being one of a plurality of static components of the client resource, the message being targeted only to a subset of the server-side logic, the subset not comprising logic for a server-side control associated with any component of the static components that is not the specific component; and

generating, by the subset, a response to the message.

23. A computer-readable medium as recited in claim 23, wherein the response does not comprise markup language.

22. A computer-readable medium as recited in claim 23, wherein the response is not a full submittal or postback of the client resource.

24. A computer-readable medium as recited in claim 23, wherein the static components comprise a form.

25. A computer-readable medium as recited in claim 23, wherein the response is an incremental update of the client resource, the incremental update not being directed to update respective ones of the static components different from the specific component.

26. A computer-readable medium as recited in claim 23, wherein the instructions for generating the response further comprise instructions for not pre-rendering or rendering information associated with any one of the static components different from the specific component.

27. A computer-readable medium as recited in claim 23, and further comprising instructions for communicating, by the server-side component, the response to a client side callback handler, the client side callback handler being configured to process data in the response as a function of the architecture of a server-side component that logically corresponds to the specific component.

28. A computer-readable medium comprising computer-executable instructions for client-side callbacks to server events, the computer-executable instructions comprising instructions for:

communicating, by a client device, a message to a targeted subset of server-side logic configured to allow user interaction with static components utilized by a Web application executing on the client device, the message identifying an event associated with one or more particular components of the static components; and

receiving by the client computing device, a response to the message, the response being generated by a one or more server controls representing a subset of the server-side logic, the subset logically corresponding only to the one or more particular components.

29. A computer-readable medium as recited in claim 28, wherein the message is not a full page post.

30. A computer-readable medium as recited in claim 28, wherein the static components comprise a form.

31. A computer-readable medium as recited in claim 28, wherein the response is not a full page postback.

32. A computer-readable medium as recited in claim 28, and further comprising, responsive to receiving the response, instructions for incrementally updating by a browser-based Web application using the static components, only portion(s) of the resource corresponding to the one or more particular components.

33. A computer-readable medium as recited in claim 28, and further comprising instructions for providing interactivity, by a Web application executing on the client device and hosting the resource, to a user during a time period from the communicating to the receiving, the interactivity being provided with respect to at least a subset of the static components that are different than the one or more particular components.

34. A server computing device for client-side callbacks to server events, the computing device comprising:

a processor; and

a memory coupled to the processor, the memory comprising computer-program instructions executable by the processor for;

receiving a message indicating an event associated with a specific component of a client resource, the specific component being one of a plurality of static components of the client resource, logic for interaction with the static components being implemented by the server; and

generating, by a server-side component paralleling at least a subset of logic of the specific component, a response to the message, server-side logic corresponding to other ones of the static components not being used to generate the response.

35. A computing device as recited in claim 34, wherein the message is not a full page post, or wherein the response is not a full page postback.

36. A computing device as recited in claim 34, wherein the static components comprise a form.

37. A computing device as recited in claim 34, wherein the response represents an incremental update of the resource, the incremental update not being directed to update of respective ones of the static components different from the specific component.

38. A computing device as recited in claim 34, wherein the computer-program instructions generating the response further comprise computer-program instructions for not pre-rendering or rendering information associated with any one of the static components different from the specific component.

39. A client device computing device comprising:

a processor; and

a memory coupled to the processor, the memory comprising computer-program instructions executable by the processor for;

communicating a message to a targeted subset of server-side logic embedded in a Universal Resource Identifier (URI), the message identifying an event associated with at least one specific component of a resource being hosted by the client device, the resource comprising a plurality of static components that include the at least one specific component;

receiving a response to the message, the response not comprising data generated by any server-side control associated with respective ones of the static components different than the specific control.

40. A computing device as recited in claim 39, wherein the response represents only data for an incremental update of portion(s) of the resource corresponding to the at least one specific component.

41. A computing device as recited in claim 39, and further comprising computer-program instructions for providing interactivity, by a Web application executing on the client device and hosting the resource, to a user during a time period from the communicating to the receiving, the interactivity being provided with respect to at least a subset of the static components that are different than the at least one specific component.