The Net is Dead&-&Easy Ajax for the masses with xajax

„Easy Ajax for the masses with xajax
A while ago I mentioned I was going to deliver a presentation on PHP and Ajax. The conference on which I delivered it took place last week on November 10. I also promised people I’d translate everything I prepared for the presentation for posting on my weblog. It took some time but here it is! If you’re interested in diving into programming your own Ajax functionality with PHP this article might be a nice starter.
Together we’ll take a look at the xajax class library for PHP. You’ll be surprised how easy it really is to create the nifty stuff you’ll find all over the internet lately. I have prepared four documented working examples on how to use xajax in real-world situations. You can study the sourcecode as well as download the whole set to do with it whatever you like. Let’s dive into xajax!“

The Net is Dead&-&Easy Ajax for the masses with xajax

The Net is Dead&-&Easy Ajax for the masses with xajax

XML.com: Tuning AJAX

„Unless you live under a rock, you’ve heard about and likely even used AJAX. Asynchronous JavaScript and XML is becoming an increasingly pervasive deployment methodology, which necessitates that people start to both understand how it works and actually consider it more seriously as an enterprise-level development tool. To that end, I will try to illustrate one method of benchmarking your AJAX applications as well as point out some of the major performance pitfalls I have encountered while developing AJAX components and applications.“

XML.com: Tuning AJAX

XML.com: Tuning AJAX

Ajaxian: PAJAJ: PHP Asynchronous Javascript and JSON

„A new PHP based Ajax framework put its hat in the ring: PAJAJ.
PAJAJ is a object oriented Ajax framework, created by Gilbert Hyatt, written in PHP5 for development of event driven PHP web applications. The framework follows 5 basic principles:
Simplicity: Everything can be done in PHP.
Various development models:
Developer develops the whole application and interface in PHP
Designer generate a pretty but dump page, and you then hook events to it to make it a real application
You design an interface as a template (example Smarty), and have the framework make html, CSS, Javascript that you pore into the template
Event Driven
Late Binding of Events: no changes need to be made to the HTML themselves
Object Oriented: There are not only objects for the Ajax plumbing, but for page elements that you are interacting with „

Ajaxian: PAJAJ: PHP Asynchronous Javascript and JSON

Ajaxian: PAJAJ: PHP Asynchronous Javascript and JSON

Rasmus Lerdorfs 30 second AJAX Tutorial

Minimal-XMLHttpRequest (AJAX) >Tutorial von Rasmus Lerdorf:

List: php-general
Subject: [PHP] Rasmus‘ 30 second AJAX Tutorial – [was Re: [PHP] AJAX & PHP]
From: Rasmus Lerdorf
Date: 2005-07-21 22:50:56
Message-ID: 42E026D0.3090601 () lerdorf ! com
[Download message RAW]

I find a lot of this AJAX stuff a bit of a hype. Lots of people have
been using similar things long before it became „AJAX“. And it really
isn’t as complicated as a lot of people make it out to be. Here is a
simple example from one of my apps. First the Javascript:

function createRequestObject() {
var ro;
var browser = navigator.appName;
if(browser == „Microsoft Internet Explorer“){
ro = new ActiveXObject(„Microsoft.XMLHTTP“);
}else{
ro = new XMLHttpRequest();
}
return ro;
}

var http = createRequestObject();

function sndReq(action) {
http.open(‚get‘, ‚rpc.php?action=’+action);
http.onreadystatechange = handleResponse;
http.send(null);
}

function handleResponse() {
if(http.readyState == 4){
var response = http.responseText;
var update = new Array();

if(response.indexOf(‚|‘ != -1)) {
update = response.split(‚|‘);
document.getElementById(update[0]).innerHTML = update[1];
}
}
}

This creates a request object along with a send request and handle
response function. So to actually use it, you could include this js in
your page. Then to make one of these backend requests you would tie it
to something. Like an onclick event or a straight href like this:

[foo]

That means that when someone clicks on that link what actually happens
is that a backend request to rpc.php?action=foo will be sent.

In rpc.php you might have something like this:

switch($_REQUEST[‚action‘]) {
case ‚foo‘:
/* do something */
echo „foo|foo done“;
break;

}

Now, look at handleResponse. It parses the „foo|foo done“ string and
splits it on the ‚|‘ and uses whatever is before the ‚|‘ as the dom
element id in your page and the part after as the new innerHTML of that
element. That means if you have a div tag like this in your page:

Once you click on that link, that will dynamically be changed to:

foo done

That’s all there is to it. Everything else is just building on top of
this. Replacing my simple response „id|text“ syntax with a richer XML
format and makine the request much more complicated as well. Before you
blindly install large „AJAX“ libraries, have a go at rolling your own
functionality so you know exactly how it works and you only make it as
complicated as you need. Often you don’t need much more than what I
have shown here.

Expanding this approach a bit to send multiple parameters in the
request, for example, would be really simple. Something like:

function sndReqArg(action,arg) {
http.open(‚get‘, ‚rpc.php?action=’+action+’&arg=’+arg);
http.onreadystatechange = handleResponse;
http.send(null);
}

And your handleResponse can easily be expanded to do much more
interesting things than just replacing the contents of a div.

-Rasmus

Rasmus Lerdorfs 30 second AJAX Tutorial