OpenLink Ajax Toolkit (OAT) Frequently Asked Questions

General

What is OAT?

The OpenLinkAJAX Toolkit is a JavaScript library which we created to enable the development of database-independent rich internet applications (RIAs). It includes a database-connectivity layer (called AJAX Database Connectivity) that sits atop XMLA, thereby providing AJAX applications with the same data-access independence historically offered by ODBC, JDBC, ADO.NET, and OLE-DB.

What is Ajax?

AJAX (Asynchronous JavaScript and XML), or Ajax, is a group of interrelated web development technologies used for creating interactive web applications. A primary characteristic is the increased responsiveness and interactivity of web pages achieved 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 performs an action. This is intended to increase the web page's interactivity, speed, functionality, and usability.

What are the benefits of Ajax?

• The ability to leverage the same interface technology no matter whether you're dealing with local or remote sites or applications.
• The ability to build standard interfaces independent of client browser, OS, and other variables.
• Using AJAX leads to deploying service-oriented enterprise applications much easier, avoiding platform localization and testing issues.
• The ability to leverage Web services using a more dynamic and rich interface than traditional browser technology.
• The ability to quickly create mash-ups to solve specific business problems using standard dynamic interfaces that front services.

What is the relationship between Ajax and Rich Internet Applications?

Rich Internet Applications (RIAs) are web applications that offer the responsiveness, "rich" features and functionality approaching that of desktop applications. Early Internet applications supported only a basic HTML graphical user interface (GUI). Though they could serve simple functions, these applications did not have the look or feel of a desktop application. The relatively slow Internet connections these applications relied on led to the term "World Wide Wait." RIAs are a result of today's more advanced technologies that allow greater responsiveness and advanced GUIs. On the other sight, AJAX allows partial page updatesmeaning updates of individual pieces of a web page without having to reload the entire page. This creates a more responsive GUI, allowing users to continue interacting with the page as the server processes requests. Additionally, Ajax performs a vital role in Web 2.0, particularly in building Web-top applications and enhancing the user's overall experience.

What are the benefits of OAT?

• Easy to use and include in different applications
• Offers rich list of complete widgets
• Offers rich list of supplemental widgets
• Includes libraries such as JSON, Cryptography, Statistics, etc.
• Easy to use Ajax DB Connectivity
• Includes a number of standalone applications for SPARQL, RDF data processing, etc.

Who is the target audience for OAT?

All application developers.

Can OAT be used in conjunction with other Frameworks?

Yes. One example is the Virtuoso ODS Framework ods_dav_vad package.

What Browsers are compatible with OAT?

OAT works in Gecko browsers (Firefox, Mozilla/SeaMonkey), IE6/7, Opera and Apple WebKit.

How is OAT Licensed?

OAT is licensed under the GNU General Public License.

Note that the only valid version of the GPL license as far as this project is concerned is the original GNU General Public License Version 2, dated June 1991.

UI Widgets and Controls

The OAT UI Widgets and Controls are divided into 2 sections:

• complete widgets
• supplemental widgets

What are OAT Controls?

ToBeDone

Why are they important?

ToBeDone

How do I use them?

ToBeDone

Are there any usage samples?

Yes. You can check our online documentation.

Data Access Framework

ToBeDone

What is Ajax Database Connectivity?

Ajax Database Connectivity is a Generic Data Access API for JavaScript that provides transparent access to SQL (via XMLA), RDF (via SPARQL), XML (via HTTP), Web Services (SOAP or REST variants over HTTP), and Free Text (via GData). It provides query results in JSON or XML and includes in-built support for XSLT and XPath/XQuery should additional local post-processing be required.

XMLA is the SOAP or REST protocol used for SQL Data Access (as per the above). SPARQL, GData, and Web Services (REST and SOAP) are the wire protocols for the respective query mechanisms.

Why is it important?

ToBeDone

What Data Source formats are supported?

ToBeDone

How is Database Independence Achieved?

ToBeDone

How do I bind data from supported data sources to Ajax controls?

ToBeDone

System Requirements

ToBeDone

GUI Aspect

ToBeDone

Data Access

ToBeDone