Tracking change and innovation in the enterprise software development community
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Posted by Stefan Tilkov on Feb 13, 2007 12:59 AM
The OASIS Web Services Reliable Exchange (WS-RX) TC has recently approved the following specification set as a Committee Draft and approved the package for public review:
For an excellent introduction to WS Reliable Messaging and WSRM Policy Assertion, see Paul Fremantle’s article here on InfoQ. Changes since then include the addition of definitions and policies for delivery assurances, and the new WS-MakeConnection specification, which was factored out of the previous WSRM specification.
Web Services Make Connection (or WS-MakeConnection for short) “describes a protocol that allows messages to be transferred between nodes implementing this protocol by using a transport-specific back-channel. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies.” An example use case for this specification would be a request/response interaction over HTTP: using WS-Addressing headers, a sender could indicate that responses are to be sent on the “back channel” (as an HTTP response). If the connection is no longer available once the receiver wants to return the response, the sender can retrieve the response later. WS-MakeConnection seems to be similar to WS-Polling, a specification that was submitted to the W3C in October 2005.
The public review started yesterday, 12 February 2007, and ends 27 February 2007; all interested parties, whether OASIS members or not, are encouraged to provide feedback.
The full list of links for the specs in various formats can be found in the announcement message.
Introducing Project Zero: Building RESTful services for your Web application
SOA Development Survival Guide
Ensuring SOA success with effective, automated control throughout the lifecycle
Rainmaking - IBM's software virtualization strategy (Jerry Cuomo CTO blog)
mirc mırc eski mirc script indir irc komutları mirc indir kameralı mirc sohbet mirc indir mırc indir mirc mırc mirc yükle mirc download islami sohbet dini sohbet islami site islami chat kelebek kelebek script kelebekscript kelebek.gen.tr kelebek.com kameralı mirc indir kameralı mirc kameralı sohbet chat chat yap chat sohbet chatsohbet çet çet sohbet çet odası sohbet kanalları izmir sohbet kanalları sohbet odaları aşk sohbet odaları chat odaları soru cevap sevgili sevgili bul arkadaş arkadaş ara arkadaş bul arkadaşlık bedava sohbet arkadaşlık sitesi arkadaşlık siteleri partner erkek arkadaş bayan arkadaş oto araba mp3 astroloji zoydak nedir cep telefonları gazete marifetname bedava domain ücretsiz domain bayii parça kontör bayiliği bayii online kontör
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
1 comment
Reply