Filthy Rich Clients and challenges

Filthy Rich Clients and challenges

Let's get to know something about RIA's - rich internet applications v/s convenational web applications. Rich seems nice ? but is that just constrained to new buzz word itself ?

In a traditional Web application, all processing is done on the server, and a new Web page is downloaded each time the user clicks.

In a Rich Internet Application,some processing is transferred to th user’s computer (“the client”).

Interestignly:

The Rich Internet Application reflects the gradual but inevitable transition of Web applications from the simple thin-client model of a traditional Web browser to a richer distributed-function model that behaves more like the desktop in a client/server model. Today these richer user experiences are being implemented with technologies such as Flash, Ajax, and Java, using standard Internet and Web protocols.

Because RIAs are significantly more complex than traditional browser-based Web applications, they pose new design, measurement, and management challenges. To implement RIAs successfully, enterprises must reevaluate their approaches to service level management (SLM) and consider several new challenges.

I'm sure, in one or the other occassion, we all have heard buzz words like: RIA aka rich internetapplications. What are they ? How they are built ? and if at all I want to build one: how they are different from conventional web applications ? Is there any real wall differentiating RIA fromOWP- old web applications ? If 'yes' then what's that key difference ?

Alright cool. But where do I find more info on this interesting topic of -Rich Internet Applications-Design, Measurement,and Management Challenges ?

>> Come right here to Download  Document on the topic