The reasons consist of:

1. ASP’s with existing applications.
2. ISV’s that have products with web-based interfaces.
3. ISV’s that have products without web-based interfaces.
4. ISV’s whose products can now be ASP’d.
5. E-commerce.
6. Financial services.  
7. Tool makers.
8. Infrastructure providers.
9. Community site providers.
10. Content providers/Media.

I’m not sure where on the hype curve we are with AJAX, but one of the open question for businesses is: why and where should you consider using AJAX? I give ten places, in declining order of urgency, where the use of AJAX should be considered. Most of this innovation will be undertaken without all of the “it’s the web!” hype of the dotcom boom. Don’t expect to see “AJAX Inside” labels on product packaging. Expect businesses instead to emphasize the improved functionality, usability and solutions that their RIA software provides.

Read the full article

Technorati Tags: Ajax, Lessons, Business

With the popularity of AJAX growing every day I’ve had the opportunity to collect and try out many more tutorials in the last several months. These examples and how-to’s represent the best tutorials that I’ve personally used or otherwise had the opportunity to work with out of the overall group. This post is intended for individuals who learn best by example. Most of the listed tutorials come complete with instructions and source code. I’ve also categorized all of the tutorials for easy browsing. Enjoy!

Read the full article

Technorati Tags: Ajax, Tutorials, Lessons, CSS, JavaScript

Check them out

Technorati Tags: Ajax, Indicators

Like many Web programmers, you have probably worked with HTML. HTML is how programmers start to work on a Web page; HTML is often the last thing they do as they finish up an application or site, and tweak that last bit of placement, color, or style. And, just as common as using HTML is the misconception about what exactly happens to that HTML once it goes to a browser to render to the screen. Before I dive into what you might think happens — and why it is probably wrong — I want you need to be clear on the process involved in designing and serving Web pages:

1. Someone (usually you!) creates HTML in a text editor or IDE.
2. You then upload the HTML to a Web server, like Apache HTTPD, and make it public on the Internet or an intranet.
3. A user requests your Web page with a browser like Firefox or Safari.
4. The user’s browser makes a request for the HTML to your Web server.
5. The browser renders the page it receives from the server graphically and textually; users look at and activate the Web page.

While this feels very basic, things will get interesting quickly. In fact, the tremendous amount of "stuff" that happens between steps 4 and 5 is what the focus of this article. The term "stuff" really applies too, since most programmers never really consider exactly what happens to their markup when a user’s browser is asked to display it:

• Does the browser just read the text in the HTML and display it?
• What about CSS, especially if the CSS is in an external file?
• And what about JavaScript — again often in an external file?
• How does the browser handle these items and how does it map event handlers, functions, and styles to that textual markup?

It turns out that the answer to all these questions is the Document Object Model. So, without further ado, let’s dig into the DOM.

Read the full tutorial

Technorati Tags: Ajax, IBM, Javascript, DOM

here are quite a few AJAX demos and examples on the web right now. While these are invaluable to learning AJAX, some people need a bit more information than just a raw piece of code. In todays environment there are many ways to learn AJAX including, books, classes, conferences, workshops and tutorials. Of these the only one that is free and accessible to everyone are web-based tutorials. The following is a list of what I consider the be the best and most helpful AJAX tutorials that I’ve found over the past year.

Read the full article

Technorati Tags: Ajax, Tutorials, Javascript, Lessons, XML, Web 2.0

Here is a link to his blog

According to I-Newswire, Tom Vendetta, a 15 year old student from just outside New Jersey has been hired by Google to work on security flaws concerning Gmail. He was found via his blog, and Google liked his experience with JavaScript and AJAX. Supposedly Tom will be receiving a “lowered salary”, placing the funds into a bank account for future education. Tom would be working from home in Jersey instead of at the GooglePlex.

Read the full article

Technorati Tags: Ajax, Google, Javascript

Gabbly (via Digg) is a new application that embeds a chat window in any web page. It seems to be based on web proxying and iframes: You think you’re looking at the target website, e.g. digg.com, but you’re actually looking at gabbly.com with an iframe for digg.com and an iframe above that for the chat window. The URL in this case is http://gabbly.com/digg.com.

Read the full article

Technorati Tags: Ajax, Ajaxian, Chat, Web 2.0, Javascript

Read the full tutorial (Italian)
Read the full tutorial (English Google Translation)

Technorati Tags: Ajax, Tutorial, Tutorials, Javascript, live, search

One of the few things that I find lacking in PHP is the ability to report the progress of a file upload. This means that file uploads, especially uploads of larger files, can be extremely frustrating for end users when they don’t know if the upload is progressing or if it has stalled or if it has even started. There are two ways around this. One is to patch PHP, Pdoru provides such a patch. Not everyone can patch PHP though. You can’t use a patch if you’re on a shared server, if you want to use ready-made binaries, if you don’t want to risk stability by using a patch or if you just don’t want to have to remember to apply the patch again every time you upgrade PHP. The other option is to use a perl script to receive the file when it’s uploaded. This is the approach used by MegaUpload. MegaUpload is what I have based my solution on, but I have added asynchronous file upload support and an AJAX upload progress bar, instead of the refreshing popup used by MegaUpload.

Read the full tutorial

Technorati Tags: Ajax, Javascript, Tutorial, Tutorials, Form, Uploading, PHP

The start of 2005 saw the rise of a relatively new technology, dubbed “Ajax” by Jesse James Garrett of Adaptive Path. Ajax stands for Asynchronous JavaScript and XML. In a nutshell, it is the use of the nonstandard XMLHttpRequest() object to communicate with server-side scripts. It can send as well as receive information in a variety of formats, including XML, HTML, and even text files. Ajax’s most appealing characteristic, however, is its “asynchronous” nature, which means it can do all of this without having to refresh the page. This allows you to update portions of a page based upon user events and provides one of the cornerstones of Rich Internet Applications (RIA) referred to in discussions of “Web 2.0.”

Read the full article

Technorati Tags: Ajax, lessons, tutorials, javascript, alistapart, XML