InfoQ Homepage API Content on InfoQ
-
Addressing Doubts about REST
Invariably, learning about REST means that you’ll end up wondering just how applicable the concept really isbeyond introductory, “Hello, World”-level stuff. In this article, Stefan Tilkov addresses 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.
-
Hypermedia in RESTful applications
One of the constraints defined for the architectural style known as REST is "hypermedia as the engine of application state". Mark Baker, well-known for being one of the first who advocated the REST style instead of the mainstream web services approach, discusses that the hypermedia constraints means in practice and why it is essential to RESTful design.
-
Talking Rails 2.0 with David Heinemeier Hansson
Ruby on Rails 2.0 is the next version of the premier web application framework for the Ruby language, after almost a full year in development. Rails 2.0 is full of great new features, bug fixes and lots of the polish expected from the team. InfoQ had the opportunity to talk with the creator of Rails, David Heinemeier Hansson, to learn what it's like to get this release out the door.
-
A Brief Introduction to REST
In this article, Stefan Tilkov provides a pragmatic introduction to REST (REpresentational State Transfer), the architecture behind the World Wide Web, and covers the key principles: Identifiable resources, links and hypermedia, standard methods, multiple representations and stateless communication.
-
Open Source WS Stacks for Java - Design Goals and Philosophy
InfoQ's Stefan Tilkov questioned lead developers of Apache Axis2, Apache CXF, Spring Web Services, JBossWS and and Sun’s Metro about their design goals, their approach towards Java and Web services standards, data binding, accessing XML, interoperability, REST support, and framework maturity. The results revealed many similarities and some noteworthy differences.
-
Interview and Book Excerpt: RESTful Web Services
Today, InfoQ publishes a sample chapter from RESTful Web Services, a book authored by Leonard Richardson and Sam Ruby. The book covers the principles of the REST style, and explains how to build RESTful applications using Java, Ruby, and Python. InfoQ's Stefan Tilkov had a chance to talk to the authors about their motivations for writing this book and their views on REST and Web services.
-
Interview: Jérome Louvel about Restlet
In this exclusive InfoQ interview, Jérome Louvel talks about Restlet, a Java framework for building Web applications following the REST architectural style. Topics covered include the reason for Restlet's existence, REST support in Web services frameworks and in Ruby on Rails, expectations for JSR 311 and Restlet's roadmap.
-
Versatile RESTful APIs Beyond XML
The world of RESTful resources that Rails firmly entered with version 1.2 naturally uses XML as its lingua franca. But there's no reason that it can't be multi-lingual, and thanks to the versatility of rails it's easy to support other standards alongside XML in our RESTful applications, potentially opening them up to a wider audience and/or reducing their bandwidth requirements.
-
Interview with Sanjiva Weerawarana: Debunking REST/WS-* Myths
InfoQ had a chance to talk to WS-* expert and WSO2 CEO Sanjiva Weerawarana, one of the fathers and a firm advocate of the WS-* architectural vision, we questioned him on the WS-* platform and his views on Microsoft's role in standardization. Sanjiva also took the opportunity to address "WS-* and REST myths".
-
Interview: Pete Lacey Criticizes Web Services
Pete Lacey, formerly working with Systinet and now with Burton Group, recently became well-known in the SOA community because of a series of blog posts starting with a very funny one entitled "S stands for Simple". In this interview, Pete talks to InfoQ about the problems he sees with Web services in general, SOAP, WSDL and UDDI, as well as advanced standards from the WS-* family.
-
The Lost Art of Separating Concerns
In a short article, well-known REST proponent Mark Baker claims the default, Web services-based approach to SOA development fails to properly separate concerns, and describes how the more generic interface used in Web architecture leads to an improvement.
-
Java, .NET, But Why Together?
The Java vs. NET war is over. In this article, Ted Neward looks at how we can leverage the strengths of each together, such as using Microsoft Office to act as a "rich client" to a Java middle-tier service, or building a Windows Presentation Foundation GUI on top of Java POJOs, or even how to execute Java Enterprise/J2EE functionality from within a Windows Workflow host.