As 2008 wraps up, there are a number of announcements and noteworthy items surrounding Dojo, DWR, Persevere, and SitePen services. Dojo was recently updated to version 1.2.3.

Security in Ajax web applications is of growing importance. While the client-server model is very useful for architecting web applications, the web security is model is not client-server, but rather a client-deputy-server model.

Prior to the popularity of the web, client/server applications often involved the creation of native applications which were deployed to clients. In this model, developers had a great deal of freedom in determining which parts of the entire client/server application would be in the client and which in the server.

In March, we introduced the SitePen Support service to provide high-quality support for Dojo, DWR and Cometd from the people who know those projects inside and out. We’re always watching to see how we can make our services better and after listening to our early support clients we’re making changes to ensure that clients are successful with the products we support.

We’re very excited about our new commercial support offering for the Dojo Toolkit, DWR, and Cometd. So what is SitePen Support and what do we have to offer? When getting started with something different or new, there’s rarely documentation or a tutorial that addresses things in quite the right way.

Palo Alto, CA – March 13, 2008. SitePen is responding to the growing demand for commercial web application assistance by launching a support service for the Dojo Toolkit, Cometd, DWR, and related web technologies.

Joe was recently interviewed by InfoQ about DWR 3.0 as a preview of his presentation on Comet and DWR at QCon. Key points about DWR 3.0 include: Offline Support (Google Gears and/or Dojo Offline) TIBCO General Interface integration Aptana Jaxer integration OpenAjax Hub, PubSub, Bayeux, etc.

From a recent interview with Kevin Hakman on Ajaxian: “I personally love the ability to write a script that runs on the server, but call it from the client as if it were running on the client. In this case Jaxer handles all the sync or async communications for you transparently, and soon will provide end-to-end debug capabilities as well.

I’ve just had a whirlwind trip to Stockholm for JFokus 2008. It was a focused conference with some really interesting presentations.