Diary of a Fence Sitting SOA Geek
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
- SOA,
Tracking change and innovation in the enterprise software development community
Posted by Scott Delap on Apr 26, 2007 01:41 PM
The DWR team has released version 2.0. DWR allows Javascript in a browser to interact with Java on a server. Version 2.0 adds a number of interesting features. Among the highlights from the press release:
Javascript Proxy APIDWR can dynamically generate JavaScript from a Java API. This is done at runtime rather than compile time, so we can use it to remote control many browsers. This makes it very easy to write things like chat applications, or anything particularly dynamic.
Reverse Ajax
DWR supports 3 ways to asynchronously transfer messages from the server to the browser: Comet (long-lived HTTP connections), Polling and Piggyback. Of these Comet and Polling are active (fast but require extra network traffic) and Piggyback is passive (slower but doesn't need extra network traffic). DWR automatically selects the best method transparently to the programmer.
Script Scope
With normal servlets there are 4 scopes; application, session, page and request. DWR2 introduces a new scope: 'script'. Script scope applies to a single web page (rather than a whole browser), however long the page lives.
Annotations
If you are using Java 5 then you can make use of the new DWR annotations. New annotations include @RemoteProxy, @DataTransferObject, @RemoteMethod and @RemoteProperty.
DWR 2 also includes security features to provide automatic protection against CSRF attacks for many configurations and defaults to a mode where XSS attacks are reduced.
The Future of Software Delivery According to visionaries Grady Booch & Erich Gamma
The Agile Business Analyst: Skills and Techniques needed for Agile
Terracotta Distributed Cache Performance Case Study
Evolutionary Design through Agile Development Podcast
Lean Software Development Governance, a whitepaper by Per Kroll and Scott Ambler
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
Platforms need interoperability. In this article Flex interoperability with JSON and XML is explored including direct mapping to chart and grid components.
Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
David Laribee discusses the purpose of ALT.NET, its mission and future.
Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.
No comments
Reply