Skip to main content

RIA !!!

Heard about the buzz word of the Web World RIA? If not, you are here in the right place. I was bit curios about the Rich Internet Application when I came across an interesting statistics. It says by the end of 2010 majority in the web application domain would migrate to RIA, and the figure mentioned precisely is 60%. Well that’s an impressive numeral, considering the web presence and the count of the web applications available right now.
RIA!!
The Rich Internet Application is a novel idea coined by macromedia in 2002. It was not known to many till few years back, but with Web 2.0 boom RIA got a solid place in the web world. The desktop applications are known for its flexibility and the responsiveness. Meanwhile the web is very famous for its reach. The RIA combines both these features, thereby giving the users the intuitive experience.
RIAs are not just about look and feel; they actually provide significant value to the enterprise. Consequently, RIA adoption is increasing day by day. See again the figures by Research and advisory firm Gartner on RIA
More on RIA
Earlier web was known as a one way communication system, where company use to showcase their details to end users. With the emergence pf web 2.0 things totally changed. Web 2.0 gave the World Wide Web altogether a different persona. Web 2.0 made the communications to happen two ways, and considers the user as king. Users can comment, rate, network, tag and lot more.
The Web 2.0 gained the popularity and it resulted in the introduction of plethora of new tools, concepts and technologies like Ajax, Adobe AIR, Adobe Flex, SilverLight, and Isomorphic SmartClient and so on. With the new technology and tools the web applications became rich and interactive. Interactive in the sense; Rich Internet applications (RIAs) have most of the characteristics of desktop applications.
What is RIA?
Years back Web was one way communication system where companies or peoples displayed their details on it for public. Web 2.0 emergence made Web to two way communication system where users can comment, tag even rate the contents.
In addition to this features Web 2.0 brought new tools/ technologies. Those include the concepts like Adobe AIR, Adobe Flex, Ajax, SilverLight, Isomorphic SmartClient and so on. These concepts made web application rich with so many features and this is why RIA comes into picture. RIAs are web applications that have most of the characteristics of desktop applications.
Why we need RIA?
RIAs are applications which make Web with a flexibility and responsiveness of a desktop application. Also if you see the history of technology, the importance of RIA can be identified. Mainframe was the initial technology. Client / Server came with more features. Then that is replaced by HTML. RIA is the new technology with lot of features.
Technology flow is Mainframe --> Client / Server --> Web (HTML) --> Web (RIA)

Comments

Post a Comment

Popular posts from this blog

Quick reference about HP QuickTestPro ..

When I started using QTP in the mid of year 2005, the 1st question came in my mind was how do the recorded scripts replay the application scenarios without our intervention. The following things help you to understand about the fundamental features in QTP. About HP QTP Automation Tool: Scripting Language: VBScript, Vendor – HP, Purpose - Regression, Data migration, GUI, Integration Testing Commonly used Automation Tools:  HP QTP , IBM Rational Robot , Segue’s Silk Test , Test complete, actiWATE, eValid, ITP, liSA, PesterCat etc Some of the Automation Frameworks used…  Record and Playback (RP)- Recording the Script in a sequence and Replaying back  Data driven (DD)– by Parameterizing all data in script  Modularity driven (MD) – by creating independent scripts that represent modules, sections, and functions of AUT.  Keyword driven (KD)- Functions mapped to Keywords  Hybrid approach – Combination of DD, KD, MD & RP Recording Modes: Standard Recording: Done by normal recording to...
Post a Comment
Read more

Problem in syncing QTP with your web application.....

You have a very simple solution ...Instead of using wait property or inserting synchronization point. The following piece of script can be made reusable action and can be called anywhere while web page is loading.. If Browser (“micclass: =browser”).page (“micclass: =page”).exist then Environment. Value (“class”) = browser (“micclass: =browser”) Else if Environment. Value (“class”) = browser (“creationtime: =1”) End if Start timer = time Set B = Environment. Value (“class”) While B.busy = true OR B.readystate 4 Set B = Environment. Value (“class”) Wait (1) Wend End timer = time If time > = 0 then Msgbox (“browser is loaded”) End if Note: In While loop, 2 properties of Browser being used.
Post a Comment
Read more

Thoughts on improving QTP execution performance by utilizing Descriptive programming (DP) .....

Some of the QTP projects/users might have experienced the following problem when their project getting huge or they need QTP execution very frequently for their product release. Problem: When repository is getting huge due to the large no of objects being added to object repository. Memory usage will be high when the Object repository size increased causing a decrease in the performance of QTP while recognizing objects. As you aware of QTP 8.2 and below Mercury recommends that OR size should not be greater than 1.5MB. Solution: Descriptive programming (DP) which does not depend on the QTP object repository features. But it stores the Application objects property values in the code itself. What is DP, how that can be achieved and when it is utilized more……… DP is nothing but avoiding QTP object repository by directly describing an object property values in the code. For example, to close a Browser, Set X = Browser (“Micclass: =Browser”) ‘code assigns Browser description to a variable. ...
Post a Comment
Read more