Ajax framework comparison

Dojo1.0.2, ext2.0.1, gwt1.4, prototype 1.5.1, jquery 1.2.3, mootools 1.2

Ajax framework classification:

1. Javascript underlying encapsulation with high degree of freedom and basic widget Components

Prototype 1.5.1,Jquery 1.2.3,Mootools 1.2

2. User-oriented widget development, no need to write too much

Ext2.0.1

3. Complete and mature framework

Dojo1.0.2,Gwt1.4,Smartclient

Advantages and disadvantages:

1. Advantage: JS files occupy a small amount, developers control them, and the scalability is high.

Disadvantage: requires a long development cycle and developers have considerable experience.

2. Advantages: rich and beautiful UI widget design, extension of CSS to change style

Disadvantage: Writing custom Widgets

3. Advantages: from underlying encapsulation to uidesign, there are good implementations

Disadvantage: the framework is too large and has a long grasp time.

Project Applicability Analysis:

1. It is too low-level and requires considerable experience and manpower.

2. The ext2.0.1 screen is called perfact. It is the most dazzling among all Ajax frameworks and has a wide range of common functions. performance bottlenecks may occur when there are too many widgets.

Demo:Http://www.dojochina.com/book/ext/examples/index.html

3. 1. Smartclient: Originally a commercial project, open-source in last November, rich widgets and demos

Demo:Http://www.smartclient.com/#_Welcome

2. Dojo1.0.2: The longest Ajax framework, from the UI widget to the chart, from the bottom layer to the top layer

Demo:Http://www.dojochina.com/dojo/demos/demoEngine.html

3. Gwt1.4: Applicable to applications with single HTML functions fully implemented by Ajax

E.g. Gmail, Google Map

Demo:Http://code.google.com/webtoolkit/examples/

• Gwt1.4: if used in a multi-page Jump project, a large number of files will be generated (one HTML generates at least 11 required files, which is not conducive to later File System Management ).

• Smartclient: It has rich UI design and mature framework system. However, because it was used as a commercial application in the past and was just open-source in last November, it lacks the foundation for use in the society.

Performance analysis:

Slickspeed

Http://mootools.net/slickspeed/

Selectors	Dojo 1.0.2	Jquery 1.2.3	Mootools 1.2beta2	Prototype 1.6.0.2
IE	230	353	795	2615
Firefox	164	255	139	252

Http://extjs.com/playpen/slickspeed /#

Selectors	Prototype 1.5.1	Jquery 1.1.3.1	Mootools 1.2 Dev	EXT 1.1rc1	Dojo Query
IE	1076	440	831	179	403
Firefox	88	291	116	212	233

EXTPerformance bottleneck:

In the past, ext was abandoned because ext had poor performance when processing a large number of controls, such as data table arrays.

Test Case:

Total loading time (seconds) directly calling action to return XML time (seconds)

20 2 <1

200 10 2

700 20 8

1400 40 17

In fact, all Ajax frameworks will encounter problems such as ext performance for a large number of grids. The reason why ext is more prominent is that it is too beautiful, resulting in too many Div layer iterations.

In web design, instead of using the DIV + CSS architecture, the reason is that iterative table is a nightmare for the running efficiency of the client, if you use too many Divs, although it is not possible to generate table iterations, it is inevitable to be quite slow.