Layer 7 Technologies has just been acquired by CA Technologies for the purpose of augmenting CA SiteMinder with Layer 7’s API Management & Security Suite. Layer 7 specializes in adding “access, security, SLA and management features” to existing service APIs.
Google has released the Mirror API for writing Glassware applications and the final specification for Glass devices.
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.
Google+ Sign-In extends the Google+ social network into third-party websites, desktop applications and mobile apps. This service, announced on February 26th, provides features for authentication, authorization and activity sharing. There is also support for user engagement, hangouts and automatic Android app downloads.
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.
Governance has reared its head up again, this time in the API community and questions have been raised about its relevance especially in organizations where innovation is the focus. This was a hot topic at the recent API Strategy and Practice conference and the debate continued in the blogosphere.
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.
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.
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.
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.
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.
Microsoft has created a new set of tools for incorporating instantaneous language translating capabilities into mobile apps.With the new Translator Hub developers gain a supple Application Programming Interface (API) for customizing Windows Phone and other operating systems to translate up to 39 languages in their unique apps. The service is on sale now to developers or it can be sampled for free.
A recent publication in the ACM CCS'12 proceedings titled "The Most Dangerous Code in the World:Validating SSL Certificates in Non-Browser Software" exposes critical vulnerabilities in the creation and usage of SSL libraries in non-browser applications. The lessons learnt and the ensuing recommendations to developers and testers are shared in this news item.
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?
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.