Home
AJAX
Interview FAQs

FAQs of level

AJAX requests should use an HTTP GET request while retrieving data where the data does not change for a given URL requested. An HTTP POST should be used when state is updated on the server. This is in line with HTTP idempotency recommendations and is highly recommended for a consistent web application architecture.

From your JavaScript clients you can access data in other domains if the return data is provide in JSON format. In essence you can create a JavaScript client that runs operates using data from a different server. This technique is know as JSON with Padding or JSONP. There are questions as to whether this method is secure as you are retrieving data from outside your domain and allowing it to be excuted in the context of your domain. 
Not all data from third parties is accessible as JSON and in some cases you may want an extra level of protection. With Java you can provide a proxy to third party services using a web component such as a servlet. This proxy can manage the communication with a third party service and provide the data to your clients in a format of your choosing. You can also cache data at your proxy and reduce trips to service. For more on using a Java proxy to create mashups see The XmlHttpProxy Client for Java.

HTML_AJAX does not have specific plans to integrate with other JavaScript libraries. Part of this is because external dependencies make for a more complicated installation process. It might make sense to offer some optional dependencies on a library like scriptaculous automatically using its visual effects for the loading box or something, but there is not a lot to gain from making default visuals like that flashier since they are designed to be easily replaceable.

A language specially designed for processing, defining and presenting text/data is called a Markup Language.

The W3C Document Object Model (DOM) is defined by the W3C as the following: The Document Object Model is a platform- and language-neutral interface.

Following are the security issues with AJAx-

  • Source code written in AJAX is easily human readable. 
  • Attackers can easily insert scripts into the system. 
  • JSON data leakage. 
  • Database detail can be obtained easily.

AJAX requests should use an HTTP GET request when retrieving data where the data will not change for a given request URL. An HTTP POST should be used when state is updated on the server. This is in line with HTTP idempotency recommendations and is highly recommended for a consistent web application architecture.

It is not necessary that AJAX applications easier to develop than traditional web applications. AJAX applications inevitably involve running complex JavaScript code on the client. Making that complex code efficient and bug-free is not a task to be taken lightly, and better development tools and frameworks will be needed to help us meet that challenge.

There is a port of JUnit for client-side JavaScript called JsUnit.

HTML_AJAX has not had a stable release yet and the pear installer does not install non stable packages by default unless you specify a version.

PreviousDisplaying 5 of 6Next
1 2 3 4 5 6
Need Help? Contact Us.

Log in

*
*

Forgot password?

*

New User

*
*
*
*