<?xml version="1.0" encoding="UTF-8"?>
<section id="ajaxdev">
- <title>AJAX client development</title>
+ <title>Ajax client development</title>
<para>
- Pazpar2 offers programmer a simple Web Service protocol that can be used (queried in a request/response fashion) from any, server- or client-side, programming language with an XML support. However, when programming a Web-based client to Pazpar2, to achieve certain level of interactivity and instant notification of latest changes in the result set, AJAX (Asynchronous JavaScript and XML) technology may be used. An AJAX client allows user to browse the results before the lengthy process of information retrieval from the back-end targets is finished. Blocking and waiting for usually slow back-end targets is one of the biggest functionality issues in a federated search engine.
+ Pazpar2 offers programmer a simple Web Service protocol that can be used (queried in a request/response fashion) from any, server- or client-side, programming language with an XML support. However, when programming a Web-based client to Pazpar2, to achieve certain level of interactivity and instant notification of latest changes in the result set, Ajax (Asynchronous JavaScript and XML) technology may be used. An Ajax client allows user to browse the results before the lengthy process of information retrieval from the back-end targets is finished. Blocking and waiting for usually slow back-end targets is one of the biggest functionality issues in a federated search engine.
</para>
<para><bridgehead>Pz2.js</bridgehead></para>
<para>
- Pazpar2 comes with a small JavaScript library called pz2.js. This library is designed to simplify development of an AJAX-based pazpar2 client and alleviate programmer from the low-level details like polling the web service, fetching and parsing returned XML output or managing timers, sessions and basic state variables.
+ Pazpar2 comes with a small JavaScript library called pz2.js. This library is designed to simplify development of an Ajax-based pazpar2 client and alleviate programmer from the low-level details like polling the web service, fetching and parsing returned XML output or managing timers, sessions and basic state variables.
</para>
<para>
<variablelist>
- <para><bridgehead>AJAX helper class</bridgehead></para>
+ <para><bridgehead>Ajax helper class</bridgehead></para>
<varlistentry><term>pzHttpRequest</term>
- <listitem><para>a cross-browser AJAX wrapper class</para></listitem></varlistentry>
+ <listitem><para>a cross-browser Ajax wrapper class</para></listitem></varlistentry>
<varlistentry><term>constructor (url, errorHandler)</term>
<listitem><para>create new request for a given url</para></listitem></varlistentry>
user management and attractive displays are expected to be implemented by
applications that use Pazpar2. Pazpar2 itself is user-interface independent.
Its functionality is exposed through a simple XML-based web-service API,
- designed to be easy to use from an AJAX-enabled browser, Flash
+ designed to be easy to use from an Ajax-enabled browser, Flash
animation, Java applet, etc., or from a higher-level server-side language
like PHP, Perl or Java. Because session information can be shared between
browser-based logic and server-side scripting, there is tremendous
possible to combine Pazpar2 either with your server-side dynamic
website scripting, with scripting or code running in the browser, or
with any combination of the two. Pazpar2 is an excellent tool for
- building advanced, AJAX-based user interfaces for metasearch
+ building advanced, Ajax-based user interfaces for metasearch
functionality, but it isn't a requirement -- you can choose to use
Pazpar2 entirely as a backend to your regular server-side scripting.
When you do use Pazpar2 in conjunction
- with browser scripting (JavaScript/AJAX, Flash, applets,
+ with browser scripting (JavaScript/Ajax, Flash, applets,
etc.), there are special considerations.
</para>
<para>
You can use Pazpar2 from any environment that allows you to use
webservices. The initial goal of the software was to support
- AJAX-based applications, but there literally are no limits to what
+ Ajax-based applications, but there literally are no limits to what
you can do. You can use Pazpar2 from Javascript, Flash, Java, etc.,
on the browser side, and from any development environment on the
server side, and you can pass session tokens and record IDs freely
<note>
<para>
The following discussion of practical issues related to session and settings
- management are cast in terms of a user interface based on AJAX/Javascript
+ management are cast in terms of a user interface based on Ajax/Javascript
technology. It would apply equally well to many other kinds of browser-based logic.
</para>
</note>
<para>
Step 1: The Javascript client loads, and asks the webserver for a new Pazpar2
session ID. This can be done using a Javascript call, for instance. Note that
- it is possible to submit AJAX HTTPXmlRequest calls either to Pazpar2 or to the
+ it is possible to submit Ajax HTTPXmlRequest calls either to Pazpar2 or to the
webserver that Pazpar2 is proxying for. See (XXX Insert link to Pazpar2 protocol).
</para>
request is forwarded to the HTTP server specified in the configuration
using the proxy setting.
This way, a regular webserver can host the user interface (itself dynamic
- or static HTML), and AJAX-style calls can be used from JS (or any other client-based
+ or static HTML), and Ajax-style calls can be used from JS (or any other client-based
scripting environment) to interact with the search logic in Pazpar2.
</para>
<para>
projects / pazpar2-moved-to-github.git / commitdiff