Riwas

Distinguish the term “Rich Internet Applications” (RIAs) from “Rich Web-based Applications” (RiWAs).  

Rich Internet applications (RIA) are Web-based applications that have some characteristics of graphical desktop applications. Built with powerful development tools, RIAs can run faster and be more engaging. They can offer users a better visual experience and more interactivity than traditional browser applications that use only HTML and HTTP. 

 

The key features of RiWAs  

RIAs as applications, which run online and have many of the features and functionalities of desktop applications. RIAs have overcome problems with traditional Web applications – such as slow performance and limited interactivity – with their responsive UIs and interactive capabilities, which make the Internet-based programs easier to be used and more functional. RIAs are Web applications, augmented with desktop features, which use mechanisms of advanced communications for data handling, to execute operations on the client-side, minimizing the server requests. RIAs are Web applications, which provide look-and-feel similar to desktop applications, thus different from the earlier generation of Web applications.  RIAs provide a variety of interactive GUI elements, the possibility of both on-line and off-line use of the application, and the transparent usage of the computing power of the client, server, and the network. RIAs are capable of processing data in both server and client, and the data exchange takes place in an asynchronous way so that the client stays responsive while continuously recalculating or updating parts of the UI, till the communication is being processed. 

  

Different technologies and techniques used to develop the client-side components  

J2EE - Java Platform, Enterprise Edition (Java EE) is the industry standard for developing portable, robust, scalable and secure server-side Java applications. Building on the solid foundation of the Standard Edition, Java EE provides web services, component model, management, and communications APIs that make it the industry standard for implementing enterprise-class web applications. 

JSP - JavaServer Pages (JSP) technology enables Web developers and designers to rapidly develop and easily maintain, information-rich, dynamic Web pages that leverage existing business systems. As part of the Java technology family, JSP technology enables rapid development of Web-based applications that are platform independent. JSP technology separates the user interface from content generation, enabling designers to change the overall page layout without altering the underlying dynamic content. 

 

Servlets - Servlets are the Java platform technology of choice for extending and enhancing Web servers. Servlets provide a component-based, platform-independent method for building Web-based applications, without the performance limitations of CGI programs. And unlike proprietary server extension mechanisms (such as the Netscape Server API or Apache modules), servlets are server- and platform-independent. This leaves you free to select a “best of breed” strategy for your servers, platforms, and tools. 

 

AJAX - Ajax is a web development technique used for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user requests a change. This is intended to increase the web page’s interactivity, speed, functionality, and usability. 

 

Adobe Flash - Adobe Flash technology is used to create content for the web applications, games and movies, and content for mobile phones and other embedded devices. The Flash Player is a client application available in most common web browsers. 

 

Model-view-controller - Model-view-controller is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction. 

 

Delta-Communication  

Delta Communications, LLC, doing business as Clearwave Communications, provides local, long distance, data, and Internet telecommunications services to residences and businesses in Southern Illinois. It offers service plans, which include mobile, dial up and high-speed Internet, and telephone systems. 

 

Advantages of Delta Modulation. The delta modulation has certain advantages over PCM as under. Since, the delta modulation transmits only one bit for one sample, therefore the signaling rate and transmission channel bandwidth is quite small for delta modulation compared to PCM. 

 

Synchronous and Asynchronous communication in the context of DC.  

Synchronous transmissions are synchronized by an external clock, while asynchronous transmissions are synchronized by        special signals along the transmission medium. 

 One of the major differences is that in synchronous transfers, senders and receivers must synchronize them  

                                  clocks before data transfer. Asynchronous transmission does not require a clock, but adds parity

bits to the data before transmission. 

 

 The distinctive characteristics of the rich communication model of the RIA are generally considered as asynchronous  

 mode, which is commonly referred to as asynchronous communication. However, asynchronous mode is controversial. 

 The rich GUI of the RIA can include multiple features on the same page. Once a page is loaded into the browser,  

 all communication with the server for all the features implemented on that page can be done using a DC, so no page  

 refresh is required. Until the page is explicitly refreshed or redirected to another page by the user or

internal component. 

 

different types of technologies and techniques available for DC  

AJAX, introducing   the   first   JS   based   rich communication   technique   for   Web   applications, overcome the   limitations of the communication model of the traditional web applications.   

        The rich communication of the RIA is handled in the background, behind the GUI of the web page, and in the user's field of view. 

          

 As client-side development techniques such as JS advance, the results are displayed in the GUI with partial rendering  

                                  of the visual content. 

 

The history and the evolution of the XHR and AJAX.  

AJAX stands for asynchronous JavaScript and XML. AJAX is not a new technology, but a technology. This is the first term written  

by James Garrett in 2005. Basically, there are many existing techniques such as HTML, CSS, JavaScript, XML, and the Document Object  

Model, and the XMLHttpRequest object is a key part. When all of these technologies work with AJAX technology, the user interface is  

updated on its own without reloading the entire web page. By default, AJAX communicates with the server and fetches data from the  server, updating the UI based on that data without reloading the entire web page. 

 

 

Before 2005, communication between client and server side was more difficult to establish. Developers use hidden iframes 

 to populate the server data on the client side. But in 2005, James Garrett wrote an article called AJAX, a

new approach  

to Web applications. The main technique used in AJAX is XMLHttpRequest (XHR). It is developed by Microsoft and used by other 

 browsers. XHR has the ability to retrieve data from the server side and populate data from the client

side with the help of   existing technologies. Prior to 2005, developers used different technologies to communicate with

the server side, such as Java  applets or Flash movies. 

 

 

Internet Explorer 5 was the first browser who introduced XHR (XMLHttpRequest) object in the internet world. Internet Explorer includes ActiveX object in MSXML library. Internet Explorer has three version of XHR object: 

 

    MSXML2.XMLHttp 

    MSXML2.XMLHttp.3.0    

MSXML2.XMLHttp.6.0 

 

The role of the DC-Bus  

The DC bus in a VFD has found its usage as the technology has evolved. Some of the applications of DC bus, Common DC applications where a single rectifier unit acts a source of power to many inverter units through common DC bus. These inverters units can be connected to many motors. A web service is any piece of software that makes itself available over the internet and uses a standardized XML messaging system. XML is used to encode all communications to a web service. For example, a client invokes a web service by sending an XML message, then waits for a corresponding XML response. 

implement it 

   Create the Web Service business logic. First, we need to write a Java class that implements the Web Service business logic. ... 

   Deploy the Java class to the SOAP server. Next, we need to turn the Java class into a Web Service. ... 

   Generate client access classes.  

   Client application development. 

 the algorithms for the request and response processing of DC. 

    

Differentiate the functions available in jQuery for implementing AJAX-based DC. 

                     Method             Description 

                     $.ajax()              Performs an async AJAX request 

                     $.get()               Loads data from a server using an AJAX HTTP GET request 

                     $.getJSON()     Loads JSON-encoded data from a server using a HTTP GET request 

   $.getScript()Loads (and executes) a JavaScript from a server using an AJAX HTTP GET request 

   $.getScript()Loads (and executes) a JavaScript from a server using an AJAX HTTP GET request 

load() Loads data from a server and puts the returned data into the selected element    serialize()     Encodes a set of form elements as a string for submission 

 

the variation of the jQuery ajax () function, explaining all the related options and events.  

This is the full list of Ajax events, and in the order in which they are triggered. The indented events are triggered for each and every Ajax request (unless a global option has been set). The ajaxStart and ajaxStop events are events that relate to all Ajax requests together. 

 

ajaxStart (Global Event) 

This event is triggered if an Ajax request is started and no other Ajax requests are currently running.    beforeSend (Local Event) 

   This event, which is triggered before an Ajax request is started, allows you to modify the XMLHttpRequest object (setting additional headers, if need be.)    ajaxSend (Global Event) 

   This global event is also triggered before the request is run. 

   success (Local Event) 

   This event is only called if the request was successful (no errors from the server, no errors with the data). 

   ajaxSuccess (Global Event) 

   This event is also only called if the request was successful. 

   error (Local Event) 

   This event is only called if an error occurred with the request (you can never have both an error and a success callback with a request). 

   ajaxError (Global Event) 

   This global event behaves the same as the local error event. 

   complete (Local Event) 

   This event is called regardless of if the request was successful, or not. You will always receive a complete callback, even for synchronous requests. 

   ajaxComplete (Global Event) 

This event behaves the same as the complete event and will be triggered every time an Ajax request finishes. 

ajaxStop (Global Event) 

This global event is triggered if there are no more Ajax requests being processed.