Rich web experience

Rich-Internet application (RIA) techniques such as AJAX, Adobe Flash and Flex have significantly improved user experience for browser-based web applications. Flash/Flex allows a part of the content of a web page to be altered without refreshing the whole page at the same time.

RIAs typically transfer the processing necessary for the user interface to the web client but keep the bulk of the data (i.e. maintaining the state of the program, the data etc) back on the application server.

RIAs typically:

• run in a web browser
• does not require software installation

Benefits of RIA

Because RIAs employ a client engine to interact with the user, they are:

• Richer.
• More responsive.
• Client/Server balance.
• Asynchronous communication.
• Network efficiency.

These benefits can be explained in detail:

Richer

They can offer user-interface behaviors not obtainable using only the HTML widgets available to standard browser-based Web applications. This richer functionality may include anything that can be implemented in the technology being used on the client side, including drag and drop, using a slider to change data, calculations performed only by the client and which do not need to be sent back to the server (e.g. an insurance rate calculator), etc.

More responsive

The interface behaviors are typically much more responsive than those of a standard Web browser that must always interact with the server.

Client/Server balance

The demand for client and server computing resources is better balanced, so that the Web server need not be the workhorse that it is with a traditional Web application. This frees server resources, allowing the same server hardware to handle more client sessions concurrently.

Asynchronous communication

The client engine can interact with the server asynchronously — that is, without waiting for the user to perform an interface action like clicking on a button or link. This option allows RIA designers to move data between the client and the server without making the user wait. Perhaps the most common application of this is pre-fetching, in which an application anticipates a future need for certain data, and downloads it to the client before the user requests it, thereby speeding up a subsequent response. Google Maps uses this technique to move adjacent map segments to the client before the user scrolls their view.

Network efficiency

The network traffic may also be significantly reduced because an application-specific client engine can be more intelligent than a standard Web browser when deciding what data needs to be exchanged with servers. This can speed up individual requests or responses because less data is being transferred for each interaction, and overall network load is reduced. However, use of asynchronous pre-fetching techniques can neutralize or even reverse this potential benefit. Because the code cannot anticipate exactly what every user will do next, it is common for such techniques to download extra data, not all of which is actually needed, to many or all clients.

There are thousands of companies in the RIA domain providing excellent innovative solutions to clients. Out of them, worth mentioning one company as it stands apart with its solutions, check out these @ Webspiders.com , a RIA based company.

You might also like to Read:

1. Mashups – the Web 2.0 way for Hybrid Apps
2. Flight Tracking using Mashup Apps and RIA
3. Google SPDY (SPeeDY): Protocol that will make web 2 times faster
4. Web 2.0
5. Web 3.0