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.
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.”
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.
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.
Back in August, we reported on the release of the Microsoft Sync Framework. Strangely enough, they recently have released it again. In honor of this bizarre event, we are following up with what information we have on this muddled framework.
In a comment on a recent InfoQ article, Bill Burke asks about the value proposition of Atom and specifically whether or not it's just a "sexier replacement" for SOAP. Bill de hOra tries to help answer the question.
With the advent of .NET 3.5 SP1 and Microsoft’s decision to support the Atom Publishing Protocol (AtomPub) for services offered by Microsoft's Live Platform, AtomPub is gaining momentum in the .NET world. In addition BlogSvc.net, an AtomPub server for WCF and .NET, features an implementation of the AtomPub protocol based on a provider model.
In a new article, ThoughtWorks' Ian Robinson discusses how consumer-driven contracts, in the form of "stories for services" and unit tests exchanged between service development streams, can strengthen the service-oriented development lifecycle. In contrast to contracts defined from the POV of the provider, consumer-driven contracts result from combining the demands of all known service consumers.