Browse Prior Art Database

OPTIMIZED CLIENT/SERVER FRAMEWORK FOR IMPLEMENTING FASTER HTML RENDERING

IP.com Disclosure Number: IPCOM000236759D
Publication Date: 2014-May-14

Publishing Venue

The IP.com Prior Art Database

Related People

Lokesh Kumar Nandagopal: AUTHOR

Abstract

A solution is provided that renders Hypertext Markup Language (HTML) faster using optimized techniques on the client and server side with a framework which decides automatically which portions of HTML / JavaServer Pages (JSP) need to be rendered on the client side and which portions need to be rendered on the server side.

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

Page 01 of 13

OPTIMIZED CLIENT/SERVER FRAMEWORK FOR IMPLEMENTING FASTER HTML RENDERING

AUTHOR:

Lokesh Kumar Nandagopal

CISCO SYSTEMS, INC.

ABSTRACT

    A solution is provided that renders Hypertext Markup Language (HTML) faster using optimized techniques on the client and server side with a framework which decides automatically which portions of HTML / JavaServer Pages (JSP) need to be rendered on the client side and which portions need to be rendered on the server side.

DETAILED DESCRIPTION

    HTML code rendering typically occurs on the client side. For example, frameworks such as DOJO and JQUERY render the User Interface (UI) on the client side. In addition to the client side, the server side could also be used to render HTML code. If both the client and server side are used for HTML rendering, the decision of whether to select the client or the server side may be based upon a set of parameters, allowing rendering of the UI to occur automatically, at either the client side or the server side based upon the environment. The solution presented herein provides a way to decide whether to render HTML on the server side and/or the client side.

    Frameworks, e.g., Zazl, etc., load the HTML/javascript into the server and generally require styles to be loaded from the client, unlike the solution presented herein. Such frameworks may even require manually entry or annotation of the parts of the code which need to be rendered from the server side. The solution presented herein automatically determines which part of the code needs to be rendered on the client side and which part of the code needs to be rendered on the server side, including styling information.

Copyright 2014 Cisco Systems, Inc.

1


Page 02 of 13

    In this solution, there is a server side and a client side framework which decides which part of the UI needs to be rendered on the server side and which part needs to be rendered on the client side. The server side framework, which takes the result set of data and the style of the UI component, will automatically generate HTML tag contents and styles which can be directly rendered on the client side without any processing on the client side. For example, for the DOJO/JQUERY datagrid or even a simple HTML table tag, the contents of the datagrid or table will usually be filled on the client side. In contrast, the solution presented herein allows the contents of the datagrid to be rendered on the server side in addition to the client side.

    As an example, the generation of or tags (which are internal to the DOJO or JQUERY datagrid) will occur on the server side as well as the client side, based upon the set of parameters. The framework presented herein will automatically determine which part needs to be rendered on the client side and which part needs to be rendered on the server side.

    For a simple DOJO datagrid, a

tag may be entered and remaining data will be populated on the client side, once data from web services is received. Population of the DOJO data...