The Art of Anwsering
May 19, 2019
0

Rich web application
A Rich Web Application(RiWA) which is originally called a Rich Internet Application (RIA) is a Web application with a significant number of indistinguishable highlights and appearances from a work area application. A RIA requires a program, program module or virtual machine to convey a client application. Information control is dealt with by the server, and UI and related item control are taken care of by the customer machine.
key features of Rich Web-based Applications
Contingent upon the application and system qualities, RIAs can frequently perform superior to customary applications. Specifically, applications that maintain a strategic distance from round outings to the server by handling locally on the customer are probably going to be quicker detectable. Offloading such preparing to the customer machines can likewise improve server execution.
2. Better feedback
In light of their capacity to change portions of pages without reloading, RIAs can furnish the client with quick and exact input, ongoing affirmation of activities and decisions, and educational and point by point mistake messages.
3. Direct interaction
In a traditional page-based Web application, interaction is limited to a small group of standard controls: check boxes, radio buttons and form fields. But RIA can use a wider range of controls that allow greater efficiency and enhance the user experience.
4. Partial-page updating
Standard HTML-based Web pages are stacked once. On the off chance that you update something on a page, the change must be sent back to the server, which rolls out the improvements and after that resend the whole page. There's no other method to do it with HTTP and HTML. With customary Web-based applications, organize availability issues, handling constraints and different issues expect clients to pause while the whole page reloads. Indeed, even with broadband associations, hold up times can be long and problematic.
5. Offline use
REFERENCES
[1] https://www.computerworld.com/article/2551058/rich-internet-applications.html
[2] https://stackoverflow.com/questions/2055430/list-of-rich-web-application-technologies
[3] https://www.quora.com/What-is-the-difference-between-Ajax-request-and-XHR-request
[4] http://api.jquery.com/category/ajax/
When connectivity is unavailable, it might still be possible to use an RIA if the app is designed to retain its state locally on the client machine.
Technologies and Techniques
Silverlight : Works best with .NET platform. Wouldn't consider to join it with Java, Ruby on Rails, PHP or something. Tools are commercial.
JavaFX / Java Applet : It's rather experimental, graphical tools and IDE are poor. The idea is to declarative (but not XML) code swing interface and run it as applet.
Flash/Flex (Flash Platform) : The most mature one. Works with all server side technologies using simple Http service, Web Service byte the best integration is by AMF services (efficient binary protocol). Integration is on different levels. Basic remote calls (it's enough for 90% projects) are available for all platforms (.NET, Java EE, PHP, RoR). but there are library for hi-level iteration (data synchronization, data push, client-server events or even client-server dependency injection) for Java EE : Adobe Life cycle Data Services (commercial) or GraniteDS and Tide Framework (free, works which JBoss Seam). Flex SDK (compiler and lib) is free, but Flex-builder is commercial.
Adobe AIR : AIR stands for Adobe Integrated Run time which run Flex or HTML+JavaScript applications on desktop (works similar to java Virtual Machine + WebStart). For flex applications integrations with remote systems are the same as above. AIR application is installed on client machine like and runs like any app. Have access to file system too. AIR runs on Windows, Mac and Linux/BSD too.
DELTA-COMMUNICATION TECHNOLOGIES
Simple-Pull-Delta-Communication (SPDC):
•Used in AJAX
•Single XHR request to the server
•Client-side: Native JS support
•Server-side: special technology is not needed
Polling is used to simulate data-push
•Send XHR requests periodically to the server
•Client-side: Native JS support
•Server-side: special technology is not needed
•Can increase network traffic (less scalable)
•Blank responses can waste resources
Web Socket (WS) is bi-directional
•Supports both data-pull and true data-push
•Client-side: HTML5 provides native JS support
Server-side: Need a WS server. Complex.
•Reduce network traffic than polling/Comet/SSE(highly scalable, 10CK is addressed)
Comet is used to simulate data-push
• Long-lived XHR requests
•Client-side: Native JS support
•Server-side: Need a streaming server. Special technology is not needed, can be implemented with standard web technologies
•Reduce network traffic than polling (more scalable)
•Blank responses are eliminated
Architecture
XHR & AJAX
The client-side controller contains the event handlers for the GUI. The events are triggered at the GUI of the Views. Views are in the client-side. subsequently, the events are triggered at the client-side. Some business-rationale are not very information driven, complex, or basic. Structures approvals, GUI components controls. They can be actualized in client-side. Client-side controller and model lessen the round outings to the server. Subsequently, improve the exhibition and increment the adaptability.
The DC bus in a VFD has discovered its utilization as the innovation has developed. A portion of the uses of DC bus, Common DC applications where a solitary rectifier unit acts a wellspring of capacity to numerous inverted units through normal DC bus.
XHR & AJAX

XMLHttpRequest (XHR) is an API available to web browser scripting languages such as JavaScript. It is used to send HTTP or HTTPS requests to a web server and load the server response data back into the script. And for AJAX request, an Ajax call is an asynchronous request initiated by the browser that does not directly result in a page transition.
An Ajax ("Asynchronous Javascript and XML") request is sometimes called an XHR request ("XmlHttpRequest"), which is the name most browsers give the object used to send an Ajax request, because at least initially Ajax calls involved the sending and receiving of XML but now it's just as common to send/receive JSON, plain text or HTML.
1. jQuery.ajax() : Perform an asynchronous HTTP(Ajax) request.
2. jQuery.get() : Load data from the server using a HTTP GET request.
3. jQuery.getJSON() : Load JSON-encoded data from the server using a GET HTTP request.
4. jQuery.getScript() : Load a JavaScript file from the server using a GET HTTP request, then execute it.
5. jQuery.post() : Load data from the server using a HTTP POST request.
6. serialize() : Encode a set of form elements as a string for submission.
7. load() : Load data from the server and place the returned HTML into the matched elements.
An Ajax ("Asynchronous Javascript and XML") request is sometimes called an XHR request ("XmlHttpRequest"), which is the name most browsers give the object used to send an Ajax request, because at least initially Ajax calls involved the sending and receiving of XML but now it's just as common to send/receive JSON, plain text or HTML.
jQuery ajax() function

2. jQuery.get() : Load data from the server using a HTTP GET request.
3. jQuery.getJSON() : Load JSON-encoded data from the server using a GET HTTP request.
4. jQuery.getScript() : Load a JavaScript file from the server using a GET HTTP request, then execute it.
5. jQuery.post() : Load data from the server using a HTTP POST request.
6. serialize() : Encode a set of form elements as a string for submission.
7. load() : Load data from the server and place the returned HTML into the matched elements.
REFERENCES
[1] https://www.computerworld.com/article/2551058/rich-internet-applications.html
[2] https://stackoverflow.com/questions/2055430/list-of-rich-web-application-technologies
[3] https://www.quora.com/What-is-the-difference-between-Ajax-request-and-XHR-request
[4] http://api.jquery.com/category/ajax/








