|
|
Rich Internet Application |
| |
have to pass through the server that is
unnecessary and lowers the processing speed.
On the other hand, RIAs can dodge this slow
and synchronous loop for many user interactions. This difference is rather similar to
the difference between “terminal and mainframe”
and Client-server/Fat client approaches.
As the development of Internet standards have
held gradually but continuously according to
turning time, it is very difficult to draw a strict
line between the composition materials of an
RIA.
But one characteristic is similar in all RIAs as
they introduce an intermediary layer of code
between the user and the server that is often
known as a client engine. It acts as an extension
of the browser and generally downloaded at
the beginning of the application that can be supplemented by further code downloads as
the application progresses. The client engine
usually takes over responsibility for rendering
the application’s user interface and for server
communication. In most RIAs the client engine
performs additional asynchronous communications with servers.
Benefits
There are several benefits of RIAs over
Traditional Web Application; these are:
|
|
- RIAs are usually richer in functionality
as they offer user-interface behaviors
using only the HTML widgets that can
include any technology being used by
the client side, including drag and drop,
using a slider to change data, calculations
performed only by the client and not
need to be sent back to the server.
- The interface behaviors of RIAs are
usually much more responsive in the
comparison of interface behaviors of a
standard Web browser while it can also
generate other performance benefits
when it uses a client engines. These are:
- It is able to make better balance
between Client and Server that frees
server resources allowing the same server
hardware to handle more client sessions
concurrently.
- It is also be able to make asynchronous
communication without waiting for the
user to perform an interface action like
clicking on a button or link. So the RIA
designers feel free to move data between
the client and the server without making
the user wait. Besides this prefetching is
the most common application, in which
an application anticipate a future need for
certain data, and downloads it to the
client before the user requests it, because
of running at high speed and getting up
a consequent response. Google Maps
uses this technology with efficiently and
on the massive scale to move adjacent
map segments to the client before the
user scrolls their view
There is another benefit of RIA in terms of
network efficiency as the huge traffic
significantly reduces in Rich Internet
Applications because an application-specific
client engine is more intelligent than a standard
Web browser when deciding what data needs
to be exchanged with servers. This boosts the
individual requests or responses due to less
data transferring in each interaction. Thus the
overall network load becomes reduced.
|
|
Sept 2007 | Java Jazz Up |63 |
|
| |
Pages:
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
27,
28,
29,
30,
31,
32,
33,
34,
35,
36,
37,
38,
39,
40,
41,
42,
43,
44,
45,
46,
47,
48,
49,
50,
51,
52,
53 ,
54,
55,
56,
57,
58,
59,
60,
61,
62,
63 ,
64,
65 ,
66 ,
67 ,
68 ,
69 ,
70,
71,
72,
73,
74,
75,
76,
77,
78,
Download PDF |
|
|
|
|
|
|
| |
| |
|
