For the geographical term, see ria. Rich Internet applications (RIA) are Web applications that have the features and functionality of traditional desktop applications. 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. Georges River, in the southern suburbs of Sydney (Australia) is a ria, or drowned river valley. ...
In software engineering, a web application is an application delivered to users from a web server over a network such as the World Wide Web or an intranet. ...
Application software is a subclass of computer software that employs the capabilities of a computer directly and thoroughly to a task that the user wishes to perform. ...
The user interface is the part of a system exposed to users. ...
A web browser is a software package that enables a user to display and interact with documents hosted by web servers. ...
One of the key concepts in computer programming is the idea of state, essentially a snapshot of the measure of various conditions in the system. ...
An application server is a software engine that delivers applications to client computers or devices. ...
RIAs typically:
An example of a Web browser (Mozilla Firefox) A web browser is a software application that enables a user to display and interact with text, images, videos, music and other information typically located on a Web page at a website on the World Wide Web or a local area network. ...
// Installation (or setup) of a program (including drivers) is the act and the effect of putting the program in a computer system so that it can be executed. ...
In computer security, a sandbox is a is a play item for little kids, suppliers and untrusted users. ...
History of RIAs The term "Rich Internet Application" was introduced in a Macromedia white paper in March 2002, though the concept had been around for a number of years before that under different names such as: Macromedia was an American graphics and web development software house headquartered in San Francisco, California producing such products as Macromedia Flash. ...
A white paper is an authoritative report. ...
2002 : January - February - March - April - May - June - July - August - September - October - November - December A timeline of events in the news for March, 2002. ...
Traditional web applications centered all activity around a client-server architecture with a thin client. Under this system all processing is done on the server, and the client is only used to display static (in this case HTML) content. The biggest drawback with this system is that all interaction with the application must pass through the server, which requires data to be sent to the server, the server to respond, and the page to be reloaded on the client with the response. By using a client side technology which can execute instructions on the client's computer, RIAs can circumvent this slow and synchronous loop for many user interactions. This difference is somewhat analogous to the difference between "terminal and mainframe" and Client-server/Fat client approaches. Remote Scripting [1] is a technology developed by Microsoft. ...
Microsoft Corporation, (NASDAQ: MSFT, HKSE: 4338) is a multinational computer technology corporation with global annual revenue of US$44. ...
Year 1998 (MCMXCVIII) was a common year starting on Thursday (link will display full 1998 Gregorian calendar). ...
October 2000 : January - February - March - April - May - June - July - August - September - October - November - December Events October 1 - 2 - Nine Israeli-Arabs are killed by Israeli security forces after a riot/violent demonstration of solidarity with Palestinians under military rule in the West Bank and Gaza. ...
Client/Server is a network application architecture which separates the client (usually the graphical user interface) from the server. ...
A HP T5700 thin client, with flash memory A Neoware m100 thin client. ...
HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. ...
A computer terminal is an electronic or electromechanical hardware device that is used for entering data into, and displaying data from, a computer or a computing system. ...
For other uses, see Mainframe. ...
Client/Server is a network application architecture which separates the client (usually the graphical user interface) from the server. ...
This article or section cites very few or no references or sources. ...
Internet standards have evolved slowly and continually over time to accommodate these techniques, so it is hard to draw a strict line between what constitutes an RIA and what does not. But all RIAs share one characteristic: they introduce an intermediate layer of code, often called a client engine, between the user and the server. This client engine is usually downloaded at the beginning of the application, and may be supplemented by further code downloads as the application progresses. The client engine acts as an extension of the browser, and usually takes over responsibility for rendering the application's user interface and for server communication.
What can be done in an RIA may be limited by the capabilities of the system used on the client. But in general, the client engine is programmed to perform application functions that its designer believes will enhance some aspect of the user interface, or improve its responsiveness when handling certain user interactions, compared to a standard Web browser implementation. Also, while simply adding a client engine does not force an application to depart from the normal synchronous pattern of interactions between browser and server, in most RIAs the client engine performs additional asynchronous communications with servers.
Benefits Because RIAs employ a client engine to interact with the user, they are: - 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, for example, a mortgage calculator.
- More responsive. The interface behaviors are typically much more responsive than those of a standard Web browser that must always interact with a remote server.
The most sophisticated examples of RIAs exhibit a look and feel approaching that of a desktop environment. Using a client engine can also produce other performance benefits: HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. ...
In computer graphical user interfaces, drag-and-drop is the action of (or support for the action of) clicking on a virtual object and dragging it to a different location or onto another virtual object. ...
Look and feel refers to design aspects of a graphical user interface - in terms of both colours, shapes, layout, typefaces, etc (the look); and, the behaviour of dynamic elements such as buttons, boxes, and menus (the feel). It is used in reference to both software and websites. ...
Information in this article or section has not been verified against sources and may not be reliable. ...
- 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 without waiting for the user to perform an interface action such as clicking on a button or link. This allows the user to view and interact with the page asynchrously from the client engine's communication with the server. 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 prefetching, 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 prefetching 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.
Google Maps (for a time named Google Local) is a free web mapping service application and technology provided by Google that powers many map-based services including the Google Maps website, Google Ride Finder and embedded maps on third-party websites via the Google Maps API. It offers street maps...
Shortcomings and restrictions Shortcomings and restrictions associated with RIAs are: - Sandbox. Because RIAs run within a sandbox, they have restricted access to system resources. If assumptions about access to resources are incorrect, RIAs may fail to operate correctly.
- Disabled scripting. JavaScript or another scripting language is often required. If the user has disabled active scripting in their browser, the RIA may not function properly, if at all.
- Client processing speed. To achieve platform independence, some RIAs use client-side scripts written in interpreted languages such as JavaScript, with a consequential loss of performance. This is not an issue with compiled client languages such as Java, where performance is comparable to that of traditional compiled languages, or with Flash movies, in which the bulk of the operations are performed by the native code of the Flash player.
- Script download time. Although it does not have to be installed, the additional client-side intelligence (or client engine) of RIA applications needs to be delivered by the server to the client. While much of this is usually automatically cached it needs to be transferred at least once. Depending on the size and type of delivery, script download time may be unpleasantly long. RIA developers can lessen the impact of this delay by compressing the scripts, and by staging their delivery over multiple pages of an application.
- Loss of integrity. If the application-base is X/HTML, conflicts arise between the goal of an application (which naturally wants to be in control of its presentation and behaviour) and the goals of X/HTML (which naturally wants to give away control). The DOM interface for X/HTML makes it possible to create RIAs, but by doing so makes it impossible to guarantee correct function. Because an RIA client can modify the RIA's basic structure and override presentation and behaviour, it can cause an irrecoverable client failure or crash. Eventually, this problem could be solved by new client-side mechanisms that granted an RIA client more limited permission to modify only those resources within the scope of its application. (Standard software running natively does not have this problem because by definition a program automatically possesses all rights to all its allocated resources).
- Loss of visibility to search engines. Search engines may not be able to index the text content of the application.
- Dependence on an Internet connection. While the ideal network-enabled replacement for a desktop application would allow users to be "occasionally connected" wandering in and out of hot-spots or from office to office, today (in 2007) the typical RIA requires network connectivity.
In computer security, a sandbox is a is a play item for little kids, suppliers and untrusted users. ...
JavaScript is a scripting language most often used for client-side web development. ...
In computer programming, an interpreted language is a programming language whose programs may be executed from source form, by an interpreter. ...
JavaScript is a scripting language most often used for client-side web development. ...
Java refers to a number of computer software products and specifications from Sun Microsystems (the Javaâ„¢ technology) that together provide a system for developing and deploying cross-platform applications. ...
Adobe Flash, or simply Flash, refers to both the Adobe Flash Player, and to the Adobe Flash Professional multimedia authoring program. ...
Web caching is the caching of web documents (e. ...
gzip is a software application used for file compression. ...
Hierarchy of objects in an example HTML DOM - Document Object Model The Document Object Model (DOM) is a platform- and language-independent standard object model for representing HTML or XML and related formats. ...
Management complications The advent of RIA technologies has introduced considerable additional complexity into Web applications. Traditional Web applications built using only standard HTML, having a relatively simple software architecture and being constructed using a limited set of development options, are relatively easy to design and manage. For the person or organization using RIA technologies to deliver a Web application, their additional complexity makes them harder to design, test, measure, and support. The software architecture of a program or computing system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships between them. ...
Use of RIA technology poses several new Service Level Management ("SLM") challenges, not all of which are completely solved today. SLM concerns are not always the focus of application developers, and are rarely if ever perceived by application users, but they are vital to the successful delivery of an online application. Aspects of the RIA architecture that complicate management processes[1] are: Wikipedia does not yet have an article with this exact name. ...
- Greater complexity makes development harder. The ability to move code to the client gives application designers and developers far more creative freedom. But this in turn makes development harder, increases the likelihood of defects (bugs) being introduced, and complicates software testing activities. These complications lengthen the software development process, regardless of the particular methodology or process being employed. Some of these issues may be mitigated through the use of a Web application framework to standardize aspects of RIA design and development. However, increasing complexity in a software solution can complicate and lengthen the testing process, if it increases the number of use cases to be tested. Incomplete testing lowers the application's quality and its reliability during use.
One could argue that the above comment applies not specifically to RIA technology, but to complexity in general. For example, that exact same argument was used when Apple and Microsoft independently announced the GUI in the 1980s, and perhaps even when Ford announced the Model T. Nonetheless, humans have shown a remarkable ability to absorb technological advances for decades, if not centuries. - RIA architecture breaks the Web page paradigm. Traditional Web applications can be viewed as a series of Web pages, each of which requires a distinct download, initiated by an HTTP GET request. This model has been characterized as the Web page paradigm. RIAs invalidate this model, introducing additional asynchronous server communications to support a more responsive user interface. In RIAs, the time to complete a page download may no longer correspond to something a user perceives as important, because (for example) the client engine may be prefetching some of the downloaded content for future use. New measurement techniques must be devised for RIAs, to permit reporting of response time quantities that reflect the user's experience. In the absence of standard tools that do this, RIA developers must instrument their application code to produce the measurement data needed for SLM.
- Asynchronous communication makes it harder to isolate performance problems. Paradoxically, actions taken to enhance application responsiveness also make it harder to measure, understand, report on, and manage responsiveness. Some RIAs do not issue any further HTTP GET requests from the browser after their first page, using asynchronous requests from the client engine to initiate all subsequent downloads. The RIA client engine may be programmed to continually download new content and refresh the display, or (in applications using the Comet approach) a server-side engine can keep pushing new content to the browser over a connection that never closes. In these cases, the concept of a "page download" is no longer applicable. These complications make it harder to measure and subdivide application response times, a fundamental requirement for problem isolation and service level management. Tools designed to measure traditional Web applications may -- depending on the details of the application and the tool -- report such applications either as a single Web page per HTTP request, or as an unrelated collection of server activities. Neither conclusion reflects what is really happening at the application level.
- The client engine makes it harder to measure response time. For traditional Web applications, measurement software can reside either on the client machine or on a machine that is close to the server, provided that it can observe the flow of network traffic at the TCP and HTTP levels. Because these protocols are synchronous and predictable, a packet sniffer can read and interpret packet-level data, and infer the user’s experience of response time by tracking HTTP messages and the times of underlying TCP packets and acknowledgments. But the RIA architecture reduces the power of the packet sniffing approach, because the client engine breaks the communication between user and server into two separate cycles operating asynchronously -- a foreground (user-to-engine) cycle, and a background (engine-to-server) cycle. Both cycles are important, because neither stands alone; it is their relationship that defines application behavior. But that relationship depends only on the application design, which cannot (in general) be inferred by a measurement tool, especially one that can observe only one of the two cycles. Therefore the most complete RIA measurements can only be obtained using tools that reside on the client and observe both cycles.
A software bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (e. ...
Software testing is the process used to measure the quality of developed computer software. ...
This does not cite any references or sources. ...
A web application framework is a software framework that is designed to support the development of dynamic websites, Web applications and Web services. ...
In software engineering, a use case is a technique for capturing the potential requirements of a new system or software change. ...
When applied to software the adjective quality may apply to source code as seen by software developers, or to applications software as seen by the end-users of the software. ...
GUI redirects here. ...
1908 Ford Model T advertisement The Model T (colloquially known as the Tin Lizzie and the Flivver) was an automobile produced by Henry Fords Ford Motor Company from 1908 through 1928. ...
Comet is a programming technique that enables web servers to send data to the client without having any need for the client to request it. ...
A packet sniffer (also known as a network analyzer or protocol analyzer or, for particular types of networks, an Ethernet sniffer or wireless sniffer) is computer software or computer hardware that can intercept and log traffic passing over a digital network or part of a network. ...
The current status of RIA development and adoption RIAs are still in the early stages of development and user adoption. There are a number of restrictions and requirements that remain: - Browser adoption: Many RIAs require modern web browsers in order to run. Advanced JavaScript engines must be present in the browser as RIAs use techniques such as XMLHTTPRequest for client-server communication, and DOM Scripting and advanced CSS techniques to enable the rich user interface.
- Web standards: Differences between web browsers can make it difficult to write an RIA that will run across all major browsers. The consistency of the Java platform, particularly after Java 1.1, makes this task much simpler for RIAs written as Java applets.
- Accessibility concerns: Additional interactivity may require technical approaches that limit applications' accessibility.
- User adoption: Users expecting standard web applications may find that some accepted browser functionality (such as the "Back" button) may have somewhat different or even undesired behaviour.
An example of a Web browser (Mozilla Firefox) A web browser is a software application that enables a user to display and interact with text, images, videos, music and other information typically located on a Web page at a website on the World Wide Web or a local area network. ...
XMLHttpRequest (XHR) is an API that can be used by JavaScript, and other web browser scripting languages to transfer XML and other text data to and from a web server using HTTP, by establishing an independent and asynchronous communication channel between a web pages Client-Side and Server-Side. ...
The term DOM Scripting refers to programatically accessing the Document Object Model (DOM). ...
“CSS†redirects here. ...
The user interface is the part of a system exposed to users. ...
A Java applet is an applet delivered in the form of Java bytecode. ...
An Ajax framework is a framework that helps to develop web applications that use Ajax, a collection of technologies used to build dynamic web pages on the client side. ...
Wikibooks has more about this subject: Curl The Curl programming language (unrelated to cURL) is a reflective programming language designed to create interactive web content. ...
Adobe Flex is a collection of technologies released by Adobe Systems for the development and deployment of cross platform, rich Internet applications based on the proprietary Adobe Flash platform. ...
Microsoft Silverlight (code-named Windows Presentation Foundation/Everywhere or WPF/E) is a proprietary XAML-based runtime for browser-based Rich Internet Applications, providing a subset of the animation, vector graphics, and video playback capabilities of Windows Presentation Foundation. ...
It has been suggested that Easy Access be merged into this article or section. ...
Justifications Although developing applications to run in a web browser is a much more limiting, difficult, and intricate a process than developing a regular desktop application, the efforts are often justified because: This article or section cites very few or no references or sources. ...
- installation is not required -- updating and distributing the application is an instant, automatically handled process
- updates/upgrades to new versions are automatic
- users can use the application from any computer with an internet connection, and usually regardless of what operating system that computer is running
- web-based applications are generally less prone to viral infection than running an actual executable
An operating system (OS) is the software that manages the sharing of the resources of a computer and provides programmers with an interface used to access those resources. ...
JavaScript The first major client side language and technology available with the ability to run code and installed on a majority of web clients was JavaScript. Although its uses were relatively limited at first, combined with layers and other developments in DHTML it has become possible to piece together an RIA system without the use of a unified client-side solution. Ajax is a new term coined to refer to this combination of techniques and has recently been used most prominently by Google for projects such as Gmail and Google Maps. However, creating a large application in this framework is very difficult, as many different technologies must interact to make it work, and browser compatibility requires a lot of effort. In order to make the process easier, several open source Ajax Frameworks have been developed, as well as commercial frameworks. JavaScript is a scripting language most often used for client-side web development. ...
Dynamic HTML or DHTML designates a technique of creating interactive web sites by using a combination of the static markup language HTML, a client-side scripting language (such as JavaScript) and the style definition language Cascading Style Sheets. ...
AJAX redirects here. ...
This article is about the corporation. ...
For other uses, see Gmail (disambiguation). ...
Google Maps (for a time named Google Local) is a free web mapping service application and technology provided by Google that powers many map-based services including the Google Maps website, Google Ride Finder and embedded maps on third-party websites via the Google Maps API. It offers street maps...
An Ajax framework is a framework that helps to develop web applications that use Ajax, a collection of technologies used to build dynamic web pages on the client side. ...
Adobe Flash, Adobe Flex and Adobe AIR Adobe Flash is another way to build Rich Internet Applications. This technology is cross-platform and quite powerful to create an application UI. Adobe Flex provides the option to create Flash user interface by compiling MXML, an XML based interface description language. Adobe is currently working on providing a more powerful platform with the product Adobe AIR, a technology combining HTMLs (including AJAX applications) Flash player based applications and PDFs. Adobe Flash, or simply Flash, refers to both the Adobe Flash Player, and to the Adobe Flash Professional multimedia authoring program. ...
Adobe Flex is a collection of technologies released by Adobe Systems for the development and deployment of cross platform, rich Internet applications based on the proprietary Adobe Flash platform. ...
MXML is an XML-based user interface markup language first introduced by the former Macromedia in March 2004. ...
The Extensible Markup Language (XML) is a general-purpose markup language. ...
Adobe Integrated Runtime (AIR), codenamed and originally named Apollo[1], is a cross-OS runtime environment for building Rich Internet Applications, using Flash, Flex, HTML, Ajax, that can be deployed as a desktop application. ...
// Ajax may refer to: Ajax the Great as a well known hero from the Trojan war and son of Telamon Ajax the Lesser son of the king of Locris, and another hero in the Trojan war Ajax (missionary), Arian missionary who converted the pagan Suevi c. ...
Microsoft Silverlight Microsoft Silverlight, which can be considered a subset of Windows Presentation Foundation (WPF) allows developers to develop RIA. Like Windows Presentation Foundation, Silverlight uses XAML. Therefore, developers with previous development experiences in the field of .NET Framework 3.0 and XAML will find Silverlight familiar, appealing and easy to use. Microsoft Silverlight (code-named Windows Presentation Foundation/Everywhere or WPF/E) is a proprietary runtime for browser-based Rich Internet Applications, providing a subset of the animation, vector graphics, and video playback capabilities of Windows Presentation Foundation. ...
This subsystem is a part of . ...
XAML (short for Extensible Application Markup Language, and pronounced Zammel) is a declarative XML-based language used to define objects and their properties, relationships and interactions. ...
Client machines need to install a small (about 2MB) plug-in (Silverlight Runtime) in order to be able to play Silverlight contents. At this time, Silverlight client for Windows and OS X is available from Microsoft. A third-party open-source plug-in called Moonlight is also available for Linux. Microsoft has also promised to broaden the range of supported clients. Moonlight is an open-source implementation of the upcoming Microsoft Silverlight runtime. ...
ActiveX Controls Embedding ActiveX controls into HTML is a very powerful way to develop rich Internet applications. However they are only guaranteed to run properly in Internet Explorer, since no other web browser at this time supports ActiveX controls. In addition, ActiveX controls are not executed in sandbox. Therefore, they are potential targets for computer viruses and malware making them high security risks. ActiveX is Microsoft technology used for developing reusable object oriented software components. ...
HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. ...
Windows Internet Explorer (formerly Microsoft Internet Explorer abbreviated MSIE), commonly abbreviated to IE, is a series of proprietary graphical web browsers developed by Microsoft and included as part of the Microsoft Windows line of operating systems starting in 1995. ...
A computer virus is a computer program that can copy itself and infect a computer without permission or knowledge of the user. ...
Malware is software designed to infiltrate or damage a computer system without the owners informed consent. ...
At the time of this writing, the Adobe Flash Player for Internet Explorer is implemented as an ActiveX control for Microsoft environments, as well as in multi-platform Netscape Plugin wrappers for the wider world. Only if corporations have standardized on using Internet Explorer as the primary web browser, is ActiveX per se a good choice for building corporate applications. ActiveX is Microsoft technology used for developing reusable object oriented software components. ...
Windows Internet Explorer (formerly Microsoft Internet Explorer abbreviated MSIE), commonly abbreviated to IE, is a series of proprietary graphical web browsers developed by Microsoft and included as part of the Microsoft Windows line of operating systems starting in 1995. ...
An example of a Web browser (Mozilla Firefox) A web browser is a software application that enables a user to display and interact with text, images, videos, music and other information typically located on a Web page at a website on the World Wide Web or a local area network. ...
OpenLaszlo OpenLaszlo is an open source rich Internet application framework developed by Laszlo Systems Inc.. The OpenLaszlo server compiles programs written in the LZX language (a mixture of XML tags and JavaScript) into either DHTML (commonly known as AJAX now) or Adobe Flash bytecode, currently supporting Flash7 and Flash8. The server - which originally was a proprietary software - was open sourced in October 2004 under the Common Public License. OpenLaszlo is the only rich Internet application platform which is capable of compiling into two different runtimes from the same code base. OpenLaszlo is an open source platform for the development and delivery of web applications with a usable human interface (sometimes called rich Internet applications) on the World Wide Web. ...
The Extensible Markup Language (XML) is a general-purpose markup language. ...
JavaScript is a scripting language most often used for client-side web development. ...
Dynamic HTML or DHTML designates a technique of creating interactive web sites by using a combination of the static markup language HTML, a client-side scripting language (such as JavaScript) and the style definition language Cascading Style Sheets. ...
// Ajax may refer to: Ajax the Great as a well known hero from the Trojan war and son of Telamon Ajax the Lesser son of the king of Locris, and another hero in the Trojan war Ajax (missionary), Arian missionary who converted the pagan Suevi c. ...
Adobe Flash, or simply Flash, refers to both the Adobe Flash Player, and to the Adobe Flash Professional multimedia authoring program. ...
The CPL (Common Public License) is a free software / open-source software license published by IBM. Its license terms have been approved by the Open Source Initiative and Free Software Foundation. ...
Curl 5.0, Rebol 2.6 and Seaside for Smalltalk Alternatives to Java and the JVM for RIA are not lacking: three alternative abstract machines are available in the form of the Curl, Rebol and Smalltalk. Curl facilitates Client-side persistent data, Rebol does not require a browser and Seaside for Smalltalk uses a minor extension to Smalltalk to provide a much richer web experience. All three alternatives are far more mature than more familiar options and as old or older than Java and the JVM. Wikibooks has more about this subject: Curl The Curl programming language (unrelated to cURL) is a reflective programming language designed to create interactive web content. ...
REBOL, the Relative Expression Based Object Language (pronounced [rebl]), is a data exchange and programming language designed specifically for network communications and distributed computing. ...
For other uses, see Small talk. ...
Seaside is an open source web application framework for developing web applications in Smalltalk. ...
JavaFX Sun Microsystems has announced JavaFX, a family of products based on Java technology designed to provide a consistent experience across a wide variety of devices including desktops, (as applets and stand-alone clients) set-top boxes, mobile devices, and Blu-Ray players. The JavaFX platform will initially comprise JavaFX Script and JavaFX Mobile. Invented by Sun Software Engineer Chris Oliver as a skunk works project, JavaFX Script enables rapid development of rich 2D interfaces using a declarative syntax similar to SVG. Sun plans to release JavaFX Script as an open source project, but JavaFX Mobile will be a commercial product available through an OEM license to carriers and handset manufacturers. JavaFX is a family of products and technologies from Sun Microsystems, first announced at the JavaOne developers conference in May 2007. ...
A modern Skunk Works project leverages an older: LASRE atop the SR-71 Blackbird. ...
SVG is also the IATA code for Stavanger Airport, Sola in Norway. ...
Java applets Java applets run in standard HTML pages and generally start automatically when their web page is opened with a modern web browser. Java applets have access to the screen (inside an area designated in its page's HTML), as well as the speakers, keyboard and mouse of any computer their web page is opened on, as well as access to the Internet, and provide a sophisticated environment capable of real time applications. A Java applet is an applet delivered in the form of Java bytecode. ...
HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. ...
Java applications Java based RIAs can be launched from within the browser or as free standing applications via Java Web Start. Java RIAs can take advantage of the full power of the Java platform to deliver rich functionality, 2D & 3D graphics, and off-line capabilities, but at the cost of delayed startup.
Numerous frameworks for Java RIAs exist, including XUL-like XML-based frameworks such as XUI, Swixml, or Canoo's thin Swing-approach, UltraLightClient. UltraLightClient is a software library that provides thin client support for Swing. ...
User Interface languages As an alternative to HTML/XHTML new user interface markup languages can be used in RIAs. For instance, the Mozilla Foundation's XML-based user interface markup language XUL - this could be used in RIAs though it would be restricted to Mozilla-based browsers, since it is not a de facto or de jure standard. The W3C's Rich Web Clients Activity[2] has initiated a Web Application Formats Working Group whose mission includes the development of such standards [3]. The original DARPA project at MIT which resulted in the W3C also resulted in the web content language Curl which is now in version 5.0. HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. ...
The Extensible HyperText Markup Language, or XHTML, is a markup language that has the same depth of expression as HTML, but also conforms to XML syntax. ...
A user interface markup language is a markup language (often XML) used to define user interfaces. ...
The Mountain View office shared by the Mozilla Foundation and the Mozilla Corporation The Mozilla Foundation (abbreviated MF or MoFo) is a non-profit organization that exists to support and provide leadership for the open source Mozilla project. ...
A user interface markup language is a markup language (often XML) used to define user interfaces. ...
XUL (pronounced zool ()), the XML User Interface Language, is an XML user interface markup language developed by the Mozilla project for use in its cross-platform applications, such as Firefox. ...
De facto is a Latin expression that means in fact or in practice. It is commonly used as opposed to de jure (meaning by law) when referring to matters of law or governance or technique (such as standards), that are found in the common experience as created or developed without...
Look up De jure in Wiktionary, the free dictionary. ...
The World Wide Web Consortium (W3C) is a consortium that produces standards—recommendations, as they call them—for the World Wide Web. ...
Wikibooks has more about this subject: Curl The Curl programming language (unrelated to cURL) is a reflective programming language designed to create interactive web content. ...
RIA's user interfaces can also become richer through the use of scriptable SVG (though not all browsers support native SVG rendering yet) as well as SMIL. SVG redirects here. ...
SMIL (pronounced or smile), the Synchronized Multimedia Integration Language, is a W3C Recommended XML markup language for describing multimedia presentations. ...
Other techniques RIAs could use XForms to enhance their functionality. XForms is two things: 1. ...
Using XML and XSLT along with some XHTML, CSS and JavaScript can also be used to generate richer client side UI components like data tables that can be resorted locally on the client without going back to the server. Mozilla and Internet Explorer browsers both support this. The Extensible Markup Language (XML) is a general-purpose markup language. ...
...
The Extensible HyperText Markup Language, or XHTML, is a markup language that has the same depth of expression as HTML, but also conforms to XML syntax. ...
“CSS†redirects here. ...
JavaScript is a scripting language most often used for client-side web development. ...
The Omnis Web Client is an ActiveX control or Netscape plug-in which can be embedded into an HTML page providing a rich application interface in the end-user's web browser. Omnis Studio is a Rapid Application Development (RAD) tool that allows programmers and application developers to create Enterprise level and Web-based applications for Windows, Linux, Solaris and Mac OS X personal computers and servers across all business sectors. ...
RIA with real-time push Traditionally, web pages have been delivered to the client only when the client requested for it. For every client request, the browser initiates an HTTP connection to the web server, which then returns the data and the connection is closed. The drawback of this approach was that the page displayed was updated only when the user explicitly refreshes the page or moves to a new page. Since transferring entire pages can take a long time, refreshing pages can introduce a long latency.
Demand for localised usage of RIA With the increasing adoption and improvement in broadband technologies, fewer users experience poor performance caused by remote latency. Furthermore one of the critical reasons for using an RIA is that many developers are looking for a language to serve up desktop applications that is not only desktop OS neutral but also installation and system issue free.
RIA running in the ubiquitous web browser is a potential candidate even when used standalone or over a LAN, with the required webserver functionalities hosted locally.
Client-side functionalities and development tools for RIA needed With client-side functionalities like Javascript and DHTML, RIA can operate on top of a range of OS and webserver functionalities.
References - ^ Rich Internet Applications: Design, Measurement, and Management Challenges, Keynote Systems, 2006 (pdf).
- ^ W3C (March 15). W3C Rich Web Clients. w3c.org.
- ^ W3C (March 15). Web Application Formats Working Group. w3c.org.
See also This is a list of rich Internet applications. ...
AJAX redirects here. ...
Adobe Flex is a collection of technologies released by Adobe Systems for the development and deployment of cross platform, rich Internet applications based on the proprietary Adobe Flash platform. ...
Adobe Integrated Runtime (AIR), codenamed and originally named Apollo[1], is a cross-OS runtime environment for building Rich Internet Applications, using Flash, Flex, HTML, Ajax, that can be deployed as a desktop application. ...
UltraLightClient is a software library that provides thin client support for Swing. ...
Comet is a programming technique that enables web servers to send data to the client without having any need for the client to request it. ...
It has been suggested that this article or section be merged with Push media. ...
Wikibooks has more about this subject: Curl The Curl programming language (unrelated to cURL) is a reflective programming language designed to create interactive web content. ...
To meet Wikipedias quality standards, this article or section may require cleanup. ...
Echo is a web framework for Swing programmers. ...
The Google Web Toolkit is an open source toolkit allowing developers to create Ajax applications in the Java programming language [1]. GWT supports rapid client/server development and debugging in any Java IDE. In a subsequent deployment step, the GWT compiler translates a working Java application into equivalent JavaScript that...
IT Mill Toolkit is a Ajax framework for developing web applications for enterprise and professional use with Java language on Server. ...
A Java applet is an applet delivered in the form of Java bytecode. ...
JavaFX is a family of products and technologies from Sun Microsystems, first announced at the JavaOne developers conference in May 2007. ...
Microsoft Silverlight (code-named Windows Presentation Foundation/Everywhere or WPF/E) is a proprietary XAML-based runtime for browser-based Rich Internet Applications, providing a subset of the animation, vector graphics, and video playback capabilities of Windows Presentation Foundation. ...
Morfik Technology Pty Ltd. ...
The introduction of this article does not provide enough context for readers unfamiliar with the subject. ...
Omnis Studio is a Rapid Application Development (RAD) tool that allows programmers and application developers to create Enterprise level and Web-based applications for Windows, Linux, Solaris and Mac OS X personal computers and servers across all business sectors. ...
OpenLaszlo is an open source platform for the development and delivery of web applications with a usable human interface (sometimes called rich Internet applications) on the World Wide Web. ...
REBOL, the Relative Expression Based Object Language (pronounced [rebl]), is a data exchange and programming language designed specifically for network communications and distributed computing. ...
Remote Scripting [1] is a technology developed by Microsoft. ...
Seaside is an open source web application framework for developing web applications in Smalltalk. ...
A single page application (SPA) is a web application that runs entirely in the client web browser, typically using a combination of HTML, JavaScript, and CSS. The application modifies the web pages own data structures through its DOM tree, and makes its changes persistent when the user invokes the...
A web desktop or webtop is a network application system for integrating web applications into a web based work space. ...
This subsystem is a part of . ...
XUL (pronounced zool ()), the XML User Interface Language, is an XML user interface markup language developed by the Mozilla project for use in its cross-platform applications, such as Firefox. ...
Wikibooks has more about this subject: ZK ZK is an open-source, all Java, Ajax Web application framework that enables rich UI for Web applications with no JavaScript and little programming. ...
External links |
Feeds |
Contact