I have published articles, and spoken at a number of industry conferences and while software development/design still remains one of my favorite activities (both professionally and as a hobby), I have found that I really enjoy writing tutorials, how-to’s etc.

So while writing is not a gift for me, I would ask that you bear with the occasional type-o as I do tend to work fast. Please feel free to point them out, and I will try and get then corrected as time permits.

Thanks!
Steve Chappell.
steve@stevechappell.com

The definition above is mine, it is by no means the ‘official’ definition of the term, but is instead the product of my experience. Take it or leave it…

What is an AsyncFW? Traditional web applications accepts data from the user and perform a ‘Submit’. The server receives the posted data, processes it, and returns an html page to the user. With an Asynchronous Framework data can be sent to the server at any time. Waiting for a response is optional.

Sound a bit like Ajax? Well it is. The AsyncFW embraces Ajax fully (as well as Comet, for server ‘push’ to client communications) . AsyncFW also includes FWDirect, our version of DWR, to allow client side access to POJO classes (Plain Old Java Objects)

Embracing the new, does not mean we have tossed out the tried and true – at it’s core the AsyncFW is a Servlet based architecture, using XSL/T. All the traditional support is built in!

For a Complete Over view

Comet is simply a mechanism for suspending a request on the server. Combine that with an Asynchronous Ajax request from the client, and you have a “fire and forget” interface to the server. The server will reply when new data is available, without the client (seemingly) needing to ask for it. The caveat being “Seemingly” – In reality, the client is simply staging the request ahead of time. Click here to read the full tutorial

The Java Messaging System presents a very interesting model for Asynchronous messaging. In essence, it provides the plumbing for sending a messages (or serializable objects) from disparate systems to a central listener which monitors the queue. Once a message is received, by the listener, it can then take some action on it. You can think of it as e-mail or Instant Messaging for applications. The listener will receive the messages in the order they were received by the Queue. Click here to read the entire tutorial