Browse Prior Art Database

A method for the web server to transfer contents and rendering method to the clients Disclosure Number: IPCOM000200357D
Publication Date: 2010-Oct-08
Document File: 5 page(s) / 72K

Publishing Venue

The Prior Art Database


Disclosed is a method for web users to view web contents without concerning how to render them. With the method described in this article, web servers can transfer not only the contents, but also the rendering method to the clients.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 5

A method for the web server to transfer contents and rendering method to the clients

There are differences among web browsers when rendering web page elements, e.g. HTML elements, CSS elements.

developers know, different browsers interprets HTML tags and their elements differently. It's also a nightmare for those web developers. When composing code, they should accommodate several kinds of browsers and of each kind, maybe several versions. To solve such problem, people found two directions: One is setting up standards, to make all web browsers render web page in a compatible way. For example, currently,

we have HTML specification and CSS specification

web developers won

--- if ( isIE6( navigator) ) {
--- --- …--- } else if ( isIE7( navigator ) ) {
--- --- …--- } else if ( isFireFox( navigator ) ) {
--- --- …--- } else {
--- --- …--- }

In the code fragment, navigator is the built-in object of Javascript. It contains the information of the web browsers user using when accessing the code.

(e.g. Button) differently according to browser type. There is still some

what if users want to share a code snippet by http request and response? One user wrote

code in Eclipse*, uploaded his code to a cloud platform and share it to a second user. The latter user then viewed the code in his browser. If

without special CSS effect, the code is only shown in text format. The latter user can't use built-in shortcuts in Eclipse and it's inconvenient to

read the code. So user needs a new way to render the code in HTTP response. For example, if the user installed Eclipse locally, by clicking the code like, his eclipse will be launched automatically and the code will be put into Eclipse editor.

Video clip is a typical example

                   . Nowadays, video clip on web page is in Flash format mainly. To play it, user need to install Flash player* plugin for their web browser, one for each browser type. If no Flash player, the video clip can't work. In this case, if web page server can provide a video player ( maybe on a cloud platform ), then even without a Flash player plugin installed, user can still view the video.

Given the above two examples, it's obvious there is need for a new way to rendering special content in web pages.

The core idea of this invention is to help server side give suggestion on which renderer to use, or even provide the renderer directly. -When sending contents to clients, the web server provides information about the suggested renderer. There could be several levels of suggestion.


As most web page

. The other is to provide specific web page for certain browser. But in practice,

't compose several versions of the same web pages. Instead, they will write one page but with a lot of the following code

Although there are several ways to rendering HTML elements

information can't be shown properly. For example,

Page 02 of 5

-For the simplest implementation, -the web server could just provide a hint on which kind of renderer to use, suc...