System and method for distributed processing of non-processable elements of a document to be rendered on a client
View Patent ↗Various systems and methods are disclosed to achieve remote processing of items in a client with limited processing capacity. Specifically, a client receives an element that it is unable to render or otherwise process to present to the user due to its limited processing capacity. The client transmits the element to a server that includes various processing modules that allow the server to process the element or otherwise perform the task that was beyond the client capability. The server thus processes the element, thereby converting it into a form that is recognizable by the client. The processed element is then sent back to the client where it is depicted or otherwise executed in the client.
1. A processing method in a server, comprising:
parsing a processing request in a server to identify a non-processable element of a document to be rendered on a client, the non-processable element being associated with the processing request, and the processing request being received from the client via a network, wherein the client is incapable of rendering the non-processable element;
consulting, in the server, a client configuration associated with the client to identify at least one processing task to be performed to convert the non-processable element into a processed element that can be rendered by the client; and
performing the at least one processing task to convert the non-processable element into the processed element that can be rendered by the client.
2. The processing method of claim 1 , further comprising generating a processing response to the processing request in the server, wherein the processed element is associated with the processing response.
3. The processing method of claim 1 , wherein the step of performing the at least one processing task further comprises converting an image from a first format into a second format, the client being capable of rendering the image embodied in the second format.
4. The processing method of claim 2 , further comprising transmitting the processing response from the server to the client via the network.
5. The processing method of claim 2 , wherein the step of generating the processing response further comprises associating the processing response with the processing request.
6. The processing method of claim 5 , wherein the step of associating the processing response with the processing request further comprises:
parsing the processing request in the server to identify a request identifier; and
including the request identifier in the processing response.
7. A program embodied on a computer readable medium for remote processing, comprising:
at least one statement for parsing a processing request in a server to identify a non-processable element of a document to be rendered on a client, the non-processable element being associated with the processing request, and the processing request being received from the client via a network, wherein the client is incapable of rendering the non-processable element; and
at least one statement for consulting a client configuration associated with the client to identify at least one processing task to be performed to convert the non-processable element into a processed element that can be rendered by the client;
at east one statement for initiating an execution of the at least one processing task to convert the non-processable element into the processed element that can be rendered by the client.
8. The program embodied on a computer readable medium of claim 7 , further comprising at least one statement for generating a processing response, wherein the processed element is associated therewith.
9. The program embodied on a computer readable medium of claim 8 , further comprising at least one statement for transmitting the processing response from the server to the client via the network.
10. The program embodied on a computer readable medium of claim 8 , wherein the at least one statement for generating the processing response further comprises at least one statement for associating the processing response with the processing request.
11. The program embodied on a computer readable medium of claim 10 , wherein the at least one statement for associating the processing response with the processing request further comprises:
at least one statement for parsing the processing request in the server to identify a request identifier; and
at least one statement for including the request identifier in the processing response.
12. A remote processing system, comprising:
a processor circuit having a processor and a memory;
remote processing logic stored in the memory and executable by the processor, the remote processing logic comprising:
logic for parsing a processing request in a server to identity a non-processable element of a document to be rendered on a client, the non-processable element being associated with the processing request, and the processing request being received from the client via a network, wherein the client is incapable of rendering the non-processable elements;
logic for consulting a client configuration stored in the memory and associated with the client to identify at least one processing task to be performed to convert the non-processable element into a processed element that can be rendered by the client; and
logic for initiating an execution of at least one processing task to convert the non-processable element into the processed element that can be rendered by the client.
13. The remote processing system of claim 12 , wherein the remote processing logic further comprises logic for generating a processing response, wherein the processed element is associated therewith.
14. The remote processing system of claim 13 , wherein the remote processing logic further comprises logic for transmitting the processing response from the server to the client via the network.
15. The remote processing system of claim 13 , wherein the logic for generating the processing response further comprises logic for associating the processing response with the processing request.
16. The remote processing system of claim 15 , wherein the logic for associating the processing response with the processing request further comprises:
logic for parsing the processing request in the server to identify a request identifier; and
logic for including the request identifier in the processing response.
17. A remote processing system, comprising:
means for parsing a processing request in a server to identify a non-processable element of a document to be rendered on a client, the non-processable element being associated with the processing request, and the processing request being received from the client via a network, wherein the client is incapable of rendering the non-processable element;
means for consulting a client configuration stored in a memory and associated with the client to identify at least one processing task to be performed to convert the non-processable element into a processed element that can be rendered by the client; and
means for initiating an execution of at least one processing task to convert the non-processable element into the processed element that can be rendered by the client.
18. The remote processing system of claim 17 , further comprising means for generating a processing response, wherein the processed element is associated therewith.
19. The remote processing system of claim 18 , further comprising means for transmitting the processing response from the server to the client via the network.
20. The remote processing system of claim 18 , wherein the means for generating the processing response further comprises means for associating the processing response with the processing request.
21. A method in a client for interfacing with a processing server, comprising:
parsing a markup file in the client to ascertain a non-processable element in the markup file, the markup file embodying a document to be rendered by the client, the markup file being received from a server via a network, wherein the client is incapable of rendering the non-processable element;
generating a processing request and associating the non-processable element therewith; and
transmitting the processing request to the processing server to be transformed into a processed element that can be rendered by the client.
22. The method of claim 21 , further comprising:
parsing a processing response received in the client from the processing server to identify the processed element associated therewith; and
rendering the processed element associated with the processing response in the client.
23. The method of claim 21 , wherein the step of generating the processing request further comprises associating a request identifier with the processing request.
24. The method of claim 21 , further comprising the step of rendering the document with the processed element embodied in the markup file in the client.
25. A program embodied on a computer readable medium for interfacing with a processing server, comprising:
at least one statement for parsing a markup file in a client to ascertain a non-processable element in the markup file, the markup file embodying a document to be rendered by the client, the markup file being received from a server via a network, wherein the client is incapable of rendering the non-processable element;
at least one statement for generating a processing request and associating the non-processable element therewith; and
at least one statement for transmitting the processing request to the processing server to be transformed into a processed element that can be rendered by the client.
26. The program embodied on a computer readable medium of claim 25 , further comprising:
at least one statement for parsing a processing response received in the client from the processing server to identify the processed element associated therewith; and
at least one statement for rendering the processed element associated with the processing response.
27. The program embodied on a computer readable medium of claim 25 , wherein the at least one statement for generating the processing request further comprises at least one statement for associating a request identifier with the processing request.
28. The program embodied on the computer readable medium of claim 25 , further comprising at least one statement for initiating a rendering of the document with the processed element embodied in the markup file in the client.
29. A system in a client for interfacing with a processing server, comprising:
a processor circuit having a processor and a memory;
processing compatibility logic stored in the memory and executable by the processor, the processing compatibility logic comprising:
logic for parsing a markup file in the client to ascertain a non-processable element in the markup file, the markup file embodying a document to be rendered by the client, the markup file being received from a server via a network, wherein the client is incapable of rendering the non-processable element;
logic for generating a processing request and associating the non-processable element therewith; and
logic for transmitting the processing request to the processing server to be transformed into a processed element that can be rendered by the client.
30. The system of claim 29 , wherein the processing compatibility logic further comprises:
logic for parsing a processing response received in the client from the processing server to identify the processed element associated therewith; and
logic for rendering the processed element associated with the processing response.
31. The system of claim 29 , wherein the logic for generating the processing request further comprises logic for associating a request identifier with the processing request.
32. The system of claim 29 , wherein the processing compatibility logic further comprises logic for initiating a rendering of the document with the processed element embodied in the markup file in the client.
33. A system in a client for interfacing with a processing server, comprising:
means for parsing a markup file in the client to ascertain a non-processable element in the markup file, the markup file embodying a document to be rendered by the client, the markup file being received from a server via a network, wherein the client is incapable of rendering the non-processable element;
means for generating a processing request and associating the non-processable element therewith; and
means for transmitting the processing request to the processing server to be transformed into a processed element that can be rendered by the client.
34. The system of claim 33 , further comprising:
means for parsing a processing response received in the client from the processing server to identify the processed element associated therewith; and
means for rendering the processed element associated with the processing response.
35. The system of claim 33 , wherein the means for generating the processing request and associating the non-processable element therewith further comprises means for associating a request identifier with the processing request.
36. The system of claim 33 , further comprising means for initiating a rendering of the document with the processed element embodied in the markup file in the client.