InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

DWR: State of the Union

Posted by Ian Roughley on Dec 18, 2007

Sections
Enterprise Architecture,
Operations & Infrastructure,
Process & Practices,
Architecture & Design,
Development
Topics
Open Source ,
Java ,
Announcements
Tags
DWR ,
AJAX
There is a lot going on in the Direct Web Remoting (DWR) world.  First and foremost is DWR joining the Dojo Foundation, and secondly is that Joe Walker, creator of DWR, has joined SitePen, Ltd. as Director of Support and Development.

For DWR users, the move to the Dojo Foundation might cause some anxiety as to the future of the project.  Alex Russel has the same concerns, and has reassured the community with the following comment:
I’ve been concerned a bit that it may appear as though Joe joining SitePen may carry with it the perception that the Dojo Foundation is an arm of SitePen in some way or that DWR will now need to become Dojo-centric. Luckily neither is the case, although reading assurances to that effect on this blog should be taken with a grain of salt. The Foundation has an open door for deserving projects which need a good legal umbrella and don’t want a lot of process or formality, and we’ve extended personal invitations to many non-Dojo-centric projects over the years to join (including direct competitors).
The move to the Dojo Foundation is progressing, but will not be immediate. Along with the code itself, there are also a whole set of organization issues to consider:
  • Moving the website to directwebremoting.org
  • Chasing down CLAs, and using a foundation CLA rather than a Getahead CLA
  • Getting lawyers to create a CLA so Getahead can grant rights to the Dojo Foundation (or something similar)
  • Get someone to pony up and let us move to SVN
  • Providing Unit tests
Further reinforcing the relationship between the Dojo foundation and DWR is Joe's new position at SitePen.  Along with SitePen's support of DWR by employing Joe to work full time with DWR, is that there will now be commercial support and services offerings around DWR. 

As far as features go, the planned 2.1 version will be skipped:
DWR 2.0 has been out for 6 months or so. At the time, I swore that the next release would be a small one, called 2.1. However it appears that I’m not good at swearing because there is lots in the next release - I think we’re going to have to call it 3.0.
So what's in DWR 3.0?
We're doing some Pub/Sub work, so DWR can be a Hub which can be used on it's own or plugged into JMS on the server-side or the OpenAjax Hub on the client. We're allowing file upload/download and some image management over DWR and adding support for JSONP and the Bayeux protocol. Another really cool feature is fairly complete version of the TIBCO GI API as a reverse ajax proxy, and I'm hoping that we can get Gears support for automatic off-line support and maybe to allow transactional remote calls. I'll be blogging about all this in more detail in a few days over at http://getahead.org/blog/joe.
Only one thing missing by Kevin Williams Posted
Re: Only one thing missing by Mike Jasnowski Posted
Re: Only one thing missing by Martin Vanek Posted
For more on where DWR is going: by Joe Walker Posted
  1. Back to top

    Only one thing missing

    by Kevin Williams

    Perhaps a link to DWR, or a definition of what DWR stands for. What is DWR?

  2. Back to top

    Re: Only one thing missing

    by Mike Jasnowski

    (D)irect (W)eb (R)emoting

  3. Back to top

    Re: Only one thing missing

    by Martin Vanek

    DWR means Demon Wielding Rakes

  4. Back to top

    For more on where DWR is going:

    by Joe Walker

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.