InfoQ Homepage Specifications Content on InfoQ
-
Bill Burke Discusses REST-*, SOA/ROA and REST
InfoQ's recent post on REST-*.org, which covered the announcement of REST-* and some of the community response to it, has drawn many responses. Changes have also been made to REST-*.org as a result of some of the feedback. Infoq had a chance to interview Bill Burke, a lead for the REST-* initiative, to learn more.
-
StoryTeller and Executable Specifications - Interview with Jeremy D. Miller
Last week Jeremy D. Miller announced a preview release of his StoryTeller project: an open source .NET project for “Executable Specifications”. InfoQ sat down with Jeremy and asked him about what StoryTeller is, how it differs from other tools like Fit/FitNesse and Cucumber, and what the future looks like for the project.
-
Is MIME a problem for REST?
In a recent blog entry Benjamin Carlyle discusses how he believes the current approach to MIME type management is a problem for greater REST adoption. He proposes a few alternatives but mentions that they do have their own problems as well.
-
Navigating the SOA Open Standards Landscape Around Architecture
Various members of the OMG, OASIS and Open Group efforts around SOA standardization have gotten together to produce a new white paper that attempts to steer you through the range of specifications and working groups. It is deliberately implementation agnostic, staying clear of Web Services, JBI and other approaches.
-
Parties Fail to Agree on the HTML 5 Video Codec
Ian Hickson, the editor of the HTML 5 Specification, has recently removed the required codecs from the video and audio tags of the respective draft standard citing difficulties in reaching consensus among major companies involved in distributing video and audio content on the web.
-
Will HTML 5 kill Flash?
As last week came to a close, the “Open Web” debate heated up after Adobe’s CEO, Shantanu Narayen, commented on how Adobe views HTML 5.
-
SOAP Over Java Messaging Service
W3C has just released Candidate Recommendation SOAP over Java Message Service 1.0, defining how SOAP should bind to a messaging system that supports the Java Message Service (JMS).
-
Location-Aware Browsing to become Mainstream?
With the W3C working on a specification that defines an API for providing scripted access to geographical location information, Mozilla recently announced built-in Geolocation support for Firefox 3.5. This is aligned with an earlier announcement from Opera that also adds support for Geolocation in their browser. Will this make geographically aware applications ubiquitous?
-
Google Releases New Version Of Protocol Buffers
Google released a new version of protocol buffers – a language-neutral, platform-neutral, extensible way of serializing structured data for use in communications protocols, data storage, and more.
-
Presentation: Ian Robinson on REST, Atom and AtomPub
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.
-
Presentation: Evolving the Java Language
Neal Gafter discusses how to evolve a widely deployed language without causing disruption using planned changes for JDK7 (superpackages, closures, annotations on types, type inference, exception handling, and self types) as an example. He examines how the changes are conditioned by preexisting language design choices, and discusses their influence on API design.
-
Presentation: Mark Nottingham's HTTP Status Report
HTTP is one of the most successful protocols in the world, and more and more developers are using it to do more than drive HTML UIs. In this presentation, recorded at QCon San Francisco 2008, HTTPbis WG chair Mark Nottingham gives an update on the current status of the HTTP protocol in the wild, and the ongoing work to clarify the HTTP specification.
-
Presentation: Steve Vinoski on REST, Reuse and Serendipity
Planning reusability is hard, designing for unforeseen reuse might be even harder. In this QCon London 2008 talk, Steve Vinoski presents some of the barriers to reuse found in typical distributed systems development approaches, and discusses how REST not only helps overcome some of these barriers, but also leads to potentially significantly increased chances for achieving serendipitous reuse.
-
JOSH: A Proposed Software Stack for the Enterprise
Grey Lens Man, a blogger who does not decline his identity, posted an interesting piece about legacy problems plaguing the enterprise and proposes a new software stack as viable solution: JOSH, JSON OSGi Scala HTTP.
-
Article: Why Do We Need Distributed OSGi?
Recently, an early release draft of a Distributed OSGi requirements and design document has been published, along with a reference implementation as part of Apache CXF. In a new article, Eric Newcomer writes about the current status of distributed OSGi and explains the reasons for standardizing it in the first place, and its significance to the OSGi specification and community.