InfoQ Homepage Languages Content on InfoQ
-
Coming From Ruby
Do you "come from" a particular programming language? If so, that's great — but don't forget to take each language on its own terms. David A. Black shares some thoughts about "coming from" a language, and the etiquette of language travel, in the context of the recent history of Ruby.
-
The MOle Plugin
The MOle, so named because it acts as the investigators agent, is a plugin that provides insight into the inner workings of Ruby on Rails in realtime, as requests come in and get processed. The author describes how the plugin came about and gives InfoQ readers a detailed introduction to his innovative plugin.
-
Adding Properties to Ruby Metaprogramatically
Werner Schuster walks us through a simple example of adding Java-style properties support (declarative getters, setters and change listeners) to Ruby classes via a Mixin by using elements of meta-programming. Introduces ideas for enhancement using principles of design-by-contract and pluggable type systems.
-
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.
-
Interview: Frank Cohen on FastSOA
InfoQ today publishes a one-chapter excerpt from Frank Cohen's book "FastSOA". On this occasion, InfoQ had a chance to talk to Frank Cohen, creator of the FastSOA methodology, about the issues when trying to process XML messages, scalability, using XQuery in the middle tier, and document-object-relational-mapping.
-
Web Applications with Spring Web Flow and Terracotta for Spring
In this article we will first give you an overview of Spring Web Flow and Terracotta for Spring, and after that show you how you can use these technologies together to enter a new dimension in writing stateful, conversational, scalable and highly available web applications.
-
Ruby on Rails case study: ChangingThePresent.org
Bruce Tate, author and CTO of ChangingThePresent.org gives a glimpse inside the day to day operations of ChangeThePresent.org with a broad overview of how his team works, the technology trusted for production environments, tools, and most important Rails frameworks.
-
Key Takeaway Points and Lessons Learned from QCon London 2007
This article presents the main takeway points and further reading as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Case studies (amazon, eBay, Yahoo!) Java, Agile, the Agile Open Space, Qualities in Architecture, Ajax and Browser Apps, .NET, Ruby, SOA, Usability, Banking Architectures followed by a summary of peoples over all opinions of QCon.
-
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.
-
Integrating Java Content Repository and Spring
Costin Leau introduces JSR 170 (Java Content Repositories) and how to integrate it with Spring Modules' JCR module, whose main objective is to simplify development with the JSR-170 API in a similar manner to that of the ORM package from the main Spring distribution.
-
Introduction to ActiveMessaging for Rails
The maintainer of ActiveMessaging for Ruby on Rails gives a comprehensive and informative introduction to his open-source framework, which enables enterprise messaging technologies to be easily integrated with Ruby on Rails applications, and is getting support from noted industry leaders such as James Strachan and Jon Tirsen.
-
10 Principles of SOA
In this article, InfoQ's Stefan Tilkov, consultant at innoQ, proposes 10 principles to serve as a basis for SOA discussions. The list starts with Don Box's four tenets (service with explicit boundaries, shared contract and schema, policy-driven, and autonomous) and expands them to include wire formats, document orientation, loose coupling, standards compliance, vendor independence, and metadata.