Rendering a first media type content on a browser

• US 20050223100A1
• Filed: 05/07/2003
• Published: 10/06/2005
• Est. Priority Date: 05/17/2002
• Status: Abandoned Application

• Current Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Original Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Inventors: Lin, Wei-Cheng, Chen, Meng-Cheng, Chen, Jeng-Chun
• Application Number:
  US10/514,292
• Publication Number:
  US 20050223100A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents

Abstract

A method, a system and a client of/for rendering a first media type (11) content on a browser (10) on a client (16) with a rendering support from a server (13). The method includes the steps of determining if the first media type content is not suitable for being rendered due to limited resources on the client, and, if this is the case activating a first software component (12) prepared for handling and receiving rendering support from the server, sending, from the client, a link to the first media type content with a request for rendering support; determining, on the server, a second media type content of the received link, wherein the second media type content is suitable for being rendered on the client; transferring the second media type content to the client; and rendering, by the first software component, the second media type content. The method further includes the steps of receiving, by the first software component, a first input event; sending the first input event from the first software component to a second software component (15) on the server; transforming, by the second software component, the received first input event to a third media type content based on the first input event and the second media type content; transferring, by the second software component, the third media type content to the first software component; and rendering the third media type content. This enables for rendering of media types on the browser on the client that the browser was not initially suitable for or did not have system resources for.

Claims

1. A method of rendering a first media type content on a browser on a client with a rendering support from a server, the method comprising the steps of:

determining if the first media type content is not suitable for being rendered due to limited resources on the client and, if this is the case, activating a first software component prepared for handling and receiving rendering support from the server;

transmitting, from the client, a link to the first media type content with a request for rendering support to the server;

determining, on the server, a second media type content of the received link, wherein the second media type content is suitable for being rendered on the client;

transferring, from the server, the second media type content to the client, in response to the received link and the request; and

rendering, by the first software component, the second media type content in response to the received second media type content.

2. A method according to claim 1, characterized in that the method further comprises the steps of:

receiving, by the first software component, a first input event;

transmitting the first input event from the first software component to a second software component on the server;

transforming, by the second software component, the received first input event to a third media type content based on the first input event and the second media type content;

transferring, by the second software component, the third media type content to the first software component; and

rendering, by the first software component, the third media type content further in response to the received third media type content.

3. A method according to claim 2, characterized in that the step of determining comprises:

determining, by the browser, that the first media type content is not renderable on the client; and

activating, if this is the case, the first software component by the browser.

4. A method according to claim 3, characterized in that the step of sending from the client comprises:

transferring, by the first software component, the link to the first media type content and the request to an application manager in the server; and

creating, by the application manager, the second software component as a plug-in application in response to the received link and request.

5. A method according to claim 4, characterized in that the step of determining, on the server a second media type content of the received link comprises:

receiving, by the second software component, a first media type content based on the received link; and

converting, by the second software component, the first media type content to a second media type content.

6. A method according to claim 5, characterized in that the first software component is a default plug-in application, wherein only a dynamic linkage library of the default plug-in application is installed on the client.

7. A method according to claim 5 characterized in that the first software component is an ActiveX control.

8. A method according to claim 7, characterized in that the first software component comprises a HTTP sub-module, a XML sub-module and a display sub-module, whereby the client is a dumb terminal.

9. A computer system for performing the method according to claim 1.

10. A computer program product comprising program code means stored on a computer readable medium for performing the method of claim 1 when the computer program is run on a computer.

11. A client for rendering a first media type content on a browser with a rendering support from a server comprising:

means for determining if the first media type content is not suitable for being rendered due to limited resources and, if this is the case, activating a first software component prepared for handling and receiving rendering support from the server;

means for transmitting a link to the first media type content with a request for rendering support to the server;

means for receiving a second media type content of the transmitted link, wherein the second media type content is suitable for being rendered on the client and wherein it is determined and transferred from the server; and

means for rendering the second media type content in response to the received second media type content.

12. A client for rendering a first media type content on a browser with a rendering support from a server according to claim 11 further comprising:

means for receiving a first input event;

means for transmitting the first input event to a second software component on the server;

means for receiving a third media type content, wherein the third media type content is transformed and transferred by the second software component, on the server, based on the received first input event and the second media type content; and

means for rendering the third media type content further in response to the received third media type content.