After a hiatus during a paper/presentation/training season, I’ve finally gone back and cleaned up the Flash/Flex versions of Hessian and BAM. The Hessian side is now updated to be compatible with the latest Hessian 2 changes. As Scott mentioned, the BAM API and protocol has undergone some changes since the last revision, so I’ve rewritten the Flash implementation of that as well. It was a surprisingly large amount of work, but I think everything is now up-to-date as well as a bit more stable.

For those that are interested, here’s a quick hello world with the new BAM API with a Flash client and a Java backend…
(more…)

As a brief respite from the training preparation, I spent yesterday fixing a slew of Hessian Flash/Flex bugs. Check out the changelog for more detailed information. This is the last snapshot that uses the old Hessian 2.0 draft spec, so you’ll need to upgrade your Java implementation for the next release/snapshot. As you might have noticed from reading the hessian-interest list, Scott’s been busy streamlining the Hessian protocol. While these changes have resulted in a number of efficiency improvements, they also break compatibility with older versions of Hessian. The next version of Hessian Flash/Flex will support this new version of the Hessian draft and only this version.

BTW, the new Hessian Flash/Flex supports the [RemoteClass] metadata, which does the same thing as the old hessianTypeName field, only better. Turns out that the Flash VM has support specifically to allow aliases for remoting. You can check out the feature request for more info.

I’ve got a couple of articles in the latest Flash & Flex Magazine about Hessian. You can even download one of them!

I’m submitting another article on using BAM with a Flash client that should hopefully be out later in the summer.

I’m working on fixing some standing bugs on the Flash and Flex versions of Hessian this week. I’m pleasantly surprised at how many people are interested in this project and happy to get bug reports. People are comparing this project to BlazeDS, which I frankly haven’t had time to look at, but it seems that some people prefer Hessian.

Here’s a quote from user Koen Serry:

Since Hessian/Burlap are really a better alternative (on a flex client) for connecting to the backend than BlazeDS (which includes IMHO way too much dependencies as well as being not very developer friendly (eg. config file over convention)). Furthermore, hessian already proved itself on the numerous java fat clients.

If you’re using Hessian Flash or Flex, please let me know! I’m interested in seeing your applications, getting bug reports, or requests for certain kinds of documentation. Koen suggested a mail application example and I’d be eager to hear any other ideas people have.

Whoops… I didn’t get a chance to post my promised posts on the new features in 3.1.5 because I was working on fixing the formatting of the blog to look more like our new website. Although, that was only part of it — I’ve spent the last few days working on a couple of magazine articles about our Hessian and Comet offering for Flash and Flex. Now that that’s done (until they send back the edits… :-)), I’m working out the presentation for AjaxWorld…