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 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.
WfXML-R is a lightweight approach to BPM that utilizes several Web 2.0 standards and protocols including Atom/AtomPub, GData, OpenSearch and OpenID/OAuth.
The Apache Abdera project, an open source Atom Syndication and Atom Publication Protocol implementation currently still in its “incubation” phase, has recently reached its 0.40 milestone, an important step towards “graduation”. InfoQ had a chance to talk to IBM's James Snell and MuleSource's Dan Diephouse, two of Abdera’s core developers, about Abdera, Atom and AtomPub.
In a new interview, recorded at QCon San Francisco, Stefan Tilkov talks to noted Web services expert and open source developer Dan Diephouse about the benefits of using the Atom Pub and Atom standards for business applications, pros and cons of using REST, and upcoming features of the Apache CXF web services stack.
Microsoft switches from the Web Structured, Schema’d & Searchable (Web3S) protocol to Atom Publishing Protocol (AtomPub) for services offered by Microsoft's Live Platform on the Web.
The Extensible Messaging and Presence Protocol (XMPP) has proven itself as a winner for instant messaging, but could it also be the protocol of choice for service integration in the future?