Monday, October 27, 2008
AjaxWorld 2008 impressions II
AjaxWorld had nearly all available conference space at the Fairmont Hotel in San José, connected by miles of carpeted classical Hotel vestibules. All talks had ample room for attending listeners, but the amount present varied (as it does) betwee different talks.
I do hope that Jaxer moves away from the server-side templating stuff and instead emphasize the really nice platform and infrastructure they have in place. Cooking DOM JS on the server and pushing the rendered results to the client when JS is unavailable or wrong version is an edge-case at best, and if no JS is present, ten attaching event-handlers won't be possible anway, so in practice (having mulled this over the course of some months) I feel that there is little that a server-side DOM processingcan do that can't be done with plain CSS anyway. Please correct me if I'm wrong :)
Something that was mentioned as a feature, jMaki made me perk my ears up. I checked jMaki out briefly a year or so ago and felt pretty certain that it was something tied to JSF, which made it rabidly uniteresting from my point of view. Luckily Greg Murray, the creator of jMaki was also present and could now refute that fact. jMaki is apparently something quite separate which can be used with Java, Ruby, PHP and now also SSJS.
All well and good, surely. But what does it do? Quite. jMaki is a cross-toolkit switchboard. What that means is that you can use a from created in Dojo, attach its events to a table from YUI which readsits data using data abstractions from Ext. Is that hot or what??? In the examples available there is always some pesky server-side component needed with generic sounding names at every turn, but it does seem at his point that jMaki is not dependent ona server-side component and of so, it is pure gold.
I also saw a presentation by Brent Hamby and Geof Hendrey from nextdb.net which takes my thin server architecture one further step: no server architecture! They have a database service which can be used directly from an ajax page with full transport security. The have a model which is similar to Kerberos, where tickets are issues and encryped by the server, which also includes rules of use which must be preserved.
Netxdb.net also have an administrative interface where you can define queries and users, in a very simple manner. If you have an applicationwhere you can put most of the logic on the client and only use a data store + security, it's a very interesting solution.
All talks were recorded, but it will take up to five weeks until we can see them online (including mine), so I'll post the links to that later.