About the Talk
September 4, 2008 7:35 AM
Berlin, GermanyBerlin, Germany
One of the big benefits of Rails is that it standardizes application development in a way you don’t see with many of the alternatives. That has made Rails applications easier and faster to develop, and much easier to maintain, than competing frameworks. This isn’t just a one-time benefit, however; with the integration of RESTful principles over the last two years, Rails applications have become even more standardized. Developers of RESTful applications can see as much of an improvement over other Rails applications as they originally saw over their old (say, PHP) sites.
This benefit, however, is not without a downside. While REST is easy to follow in the most common cases, it can be difficult to apply to some scenarios – the classic question being how to represent search RESTfully. This new approach to domain modeling can get complicated, as even one of the paradigmatic examples of RESTful Rails, the restful_authentication plugin, shows – it abandons the principles when it comes to activation.
In this session, we’ll take a look at these (and other) issues that you may encounter when you start building things outside the standard examples. From modeling complicated domains (authentication, search, and beyond), to working around the implementation of REST in Rails, we’ll discuss and apply techniques that you’ll find useful for every RESTful application you develop in the future.