BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage REST Content on InfoQ

  • WSO2 Developer Studio 3.0&3.1 Have Better ESB Tooling

    WSO2 Developer Studio 3.0 and 3.1 improve ESB and Registry Resource Editor tools, has better performance, uses Eclipse Juno SR2, and supports JAX-RS REST code generation.

  • Has Web Style Worked?

    Almost 7 years ago Tim Bray declared SOA dead and the future was Web Style. In a recent blog post Jean-Jacques Dubray looks back over the years and decides that Web Style hasn't worked and, given the plethora of non-Web Style services in the Programmable Web directory, is in fact itself dead. He also looks at what this means for computing and the future of application development.

  • Casablanca's C++ SDK Whitelisted for Open Source

    Microsoft's C++ REST SDK, codenamed Casablanca, has been open sourced under the Apache 2.0 license. Casablanca provides developers with a multiplatform way to write C++11 code that interacts with REST services.

  • Architectural Homeopathy

    In a recent article Steve Jones discussions a group of people he calls Architectural Homeopaths, who make critical architectural decisions based on "powerpoints and opinions" but with a lack of clear evidence to support them. He says they are prevalent in IT and believes that those people who push REST for enterprise integration fall into this category.

  • Getting Started with OData v3 and WCF Data Services 5.x

    If you are building new web services with .NET then OData should be high on your list of frameworks to investigate, especially if you need to support unknown third parties. The technology inherently supports both SOAP and REST style messages with the latter offering ATOM (XML) and JSON representations. This means consumers can pretty much request whatever format is best for them.

  • JAX-RS 2.0 and Bean Validation 1.1 First Java EE 7 JSRs to Win Public Approval

    Java Enterprise Edition version 7 is well under way. Late last month JSR 339 and JSR 349 were adopted by the public review ballot, making them the first two JSR's to be ratified. InfoQ spoke to Marek Potociar, JSR 339 co spec lead about the latest version of the RESTful Java API.

  • Shoehorning Java into RESTful Design

    In a recent Zapthink article the author discusses why Java and JAX-RS 2.0 are not always appropriate for building RESTful services. Much has been said about the improvements in JAX-RS 2.0 but it is the Java object model which the author believes is at the heart of at least one of the problems, with REST being shoehorned into Java or vice versa.

  • Is It Time For WADL in JAX-RS?

    At JavaOne 2012 in a panel session around the future of Java EE, the audience were keen to know whether or not WADL should be a standard part of JAX-RS. Although the panel were unable to agree, the audience appeared to be more pro WADL than against. So is this a good thing or is WADL still considered unnecessary for successful REST?

  • Microsoft Release New REST API Framework as Part of .NET 4.5

    As part of the recent Visual Studio 2012 and .NET 4.5 launch, Microsoft formally unveiled its new web services framework called the ASP.NET Web API. Included as part of the ASP.NET MVC 4 offering, the open-source ASP.NET Web API is designed to simplify the development and consumption of RESTful services.

  • IG Group Open-Sources RESTdoclet

    IG Group has open-sourced its RESTdoclet Maven plugin for generating web documentation from Spring REST based services.

  • IT Values Technologies Over Thought

    Recently Cap Gemini's Steve Jones has written an article on how he believes that thinking about solutions to problems is less important these days than jumping on the latest hype bandwagon. Although he uses REST and Big Data as examples, he believes it goes beyond any single technology and that eventually IT will no longer belong to IT people.

  • SPDY versus WebSockets?

    Lori MacVittie has recently posted an article describing why she believes SPDY will gain much wider acceptance in the Web than WebSockets. For her and several others, the differentiating aspect between these protocols is the way in which they use HTTP and SPDY wins because of this.

  • Microsoft-Led Consortium Submits OData Protocol to OASIS for Standardization

    Microsoft, along with a set of other software industry leaders, is attempting to make its data query protocol OData an industry standard. A proposal has been submitted to the Organization for the Advancement of Structured Information Standards (OASIS) with the hope of generating wider adoption of this framework.

  • Does BPM-in-the-Cloud Require RESTful Services? ZapThink Says Yes, but Doubts Exist.

    Jason Bloomberg of ZapThink claimed that cloud-based Business Process Management (BPM) software will be disruptive to those traditional BPM engines that cannot easily move to a cloud delivery model. Instead of describing the value proposition of BPM-in-the-cloud, Bloomberg’s article focused primarily on his assertion that REST-based services are a necessity for any cloudy BPM engine to work.

  • WebSockets versus REST?

    With WebSockets now a W3C Candidate Recommendation and a new JSR about to start in the JCP, the question arises about how and if WebSockets work with the principles of REST? Do they compliment each other, or will WebSockets, as some people believe, divert attention away from REST and towards a new style of interaction for the Web? There is even the suggestion that WebSockets "breaks the Web".

BT