With the sudden disappearance of _why, some popular libraries as Markaby, Hpricot and others are orphaned. We look at the effort to find maintainers for some, and at replacements for other libraries.
Christian Weyer of Thinktecture, announced the release of WSCF.blue a Visual Studio Add-in that enables contract first development of web services using WCF.
LINQ to XSD is the long awaited follow-up to LINQ to XML. Its primary purpose is to produce LINQ-compatible object models from XSD files, giving developers some measure of static type checking while accessing XML data.
In this session recorded at QCon SF 2008, Chris Berry & Bryon Jacob presented the Atom Syndication Format, the Atom Publishing Protocol, the Atom Categories, the Atom Stores, the AtomServer and how they can be used by giving a concrete example.
JRuby 1.3 will allow to reduce startup times in some situations using Nailgun. Nokogiri, a popular XML library, now runs on the latest JRuby thanks to ruby-ffi. Finally: Ruby 1.9.1-p129 is a new release that fixes a few bugs and security issues.
In a presentation, recorded at QCon San Francisco, ThoughtWorks' Ian Robinson explains how a RESTful HTTP approach can be applied in an Enterprise project. He makes use of many of the techniques that make HTTP a powerful protocol, including caching, hypermedia, and uses standard formats such as Atom Syndication for event notification.
In response to Joe Gregorio’s post, on why the browser is undermining the adoption of Atompub protocol, Sean McGrath, had an interesting take on the changing notion of what constitutes a web application.
Frank Mantek discusses the Google Data API (GData) including decisions to use REST rather than SOAP technology, how the API is used, numerous examples of how GData has been used by clients, and future plans for evolving the API. A discussion of how GData facilitates Cloud Computing concludes the presentation.
“The Atom Publishing Protocol is a failure.” Joe Gregorio says, admitting to having met his blogging-hyperbole-quotient for the day. In a post largely about the how the level of adoption that AtomPub is seeing, is far lower than the expectation. Joe writes that “There are still plenty of new protocols being developed on a seemingly daily basis, many of which could have used AtomPub, but don't.”
A few recent software releases have improved Ruby's XML support. After last years release of the Nokogiri XML library, Hpricot 0.7 has now been released with performance improvements. Also, libxml-ruby, which is built on the same XML library as Nokogiri has been released and recently caught up with Nokogiri's speed.
In this interview made during QCon SF 2008, Tim Bray talks about why he is not convinced with the buzz surrounding Rich Internet Applications and shares his ideas on Cloud Computing. He also expresses his opinion regarding the debate REST vs. WS-* and the future directions web technologies will be taking.
In his new comment, IBM’s Kyle Brown examines three different common anti-patterns, or "worst practices," that can make adopting Web Services and SOA implementations more difficult than it needs to be.
This article proposes a new Message Type Architecture to help manage the message formats in a SOA. The approach based on two related DSLs, one for the Enterprise Data Model and one for the Message Types, promotes reuse and helps aligning the Data and SOA governance processes.
Most web service developers rely on a data binding conversion layer within a web service to work directly with data structures in their programming language of choice - but this causes a number of problems. In the first of a series of articles that look at these problems, Dennis Sosnoski starts at the most basic level, looking at simple data types and the issues that arise from mapping them.
In a presentation, recorded at QCon San Francisco, MuleSource architect Dan Diephouse explores ways to use the Atom Publishing Protocol (AtomPub) when building services in a RESTful way. He explains when to use and when to avoid using AtomPub, highlights its advantages, and shows where it doesn't provide a generic solution.