API - Techniques
Get flash to fully experience Pearltrees
Vendredi c'est Grape | Bonjour gem
Si vous nous suivez depuis quelques temps vous avez pu voir pas mal de gems pour utiliser des API. C’est cool, mais si on faisait la nôtre ? :)
API - Techniques - Examples
In this post I am going to explore how you can use Goliath , an asynchronous Ruby framework to enable browser integration for services that lack JSONP api's as well as how to integrate these external services with your existing synchronous web stack.
Pale Ink: Using Goliath to Integrate With External Services
When I first started learning C++ (back in the bad old days) I was convinced that any 1st year student could design a better programming language. One which behaved in a sane fashion without a lot of legacy cruft.
API Design is UI for Developers » Terence Eden has a Blog
Putting REST on Rails
The RESTful Rails plugin adds several capabilities to normal Rails controllers that allow them to more effectively use HTTP. The focus of our example will be its most obvious feature, the per-HTTP method dispatching system.
Developing an API in Rails (jonathan spies)
At work it's finally time to open our "API" to some real use. The reason I use quotes around API is that our current implementation does almost nothing and is use by no one. But now we need a real API for our mobile apps and some future third parties.March 5, 2009 – 12:31 pm I know there are quite a few tutorials and links out there on building an API for your Ruby on Rails application, but I figured that I would document a little bit about how it was done for Riding Resource , but at a high level. A partner had requested access to some of our data via an API, and wanted the results to be spit out as XML , so here’s a little bit about how that was done.
A Real American Hero » Blog Archive » Building an API in Ruby on Rails
Creating an API // RailsTips by John Nunemaker
A few weeks back, we publicly released the Gauges API . Despite building Gauges from the ground up as an API , it was a lot of work. You really have to cross your t’s and dot your i’s when releasing an API .
I believe that restful_authentication supports this out of the box, so you can ignore whether or not someone is using your app via the API or via a browser. One downside here is that you're asking users to put their username and password in the clear in every request.
Looking for suggestions for building a secure REST API within Ruby on Rails - Stack Overflow
The restful_authentication plugin allows for user accounts, but doesn't have any API authentication built in.
Create a simple API with Ruby on Rails - Arthur Chang
I'm using Sinatra too to develop simple REST solutions. The thing is Sinatra is so flexible in many ways. You can build your project structure the way you like more.
How to create a REST API for a Ruby application? - Stack Overflow
# How to Make an API for a Rails App #
I've come across the same problem in my personal projects and also at work. You have an existing Rails app that has some authentication and authorization scheme to protect who has access to your controllers, but now you need to write an API that can access those controllers. How do you keep the same authentication routine for your API users?I'm building an XML-based webservice in Rails to serve as the backend for an iPhone app, and I'm wondering how I can best achieve an auth scheme that will let me use both GET and POST requests -- i.e. one that doesn't require auth sent in the body of an XML payload. The wrinkle here is that I'm not using regular HTTP auth.
web services - Rails XML API design practices - Stack Overflow
The Little Manual of API Design - Axon Flux // A Ruby on Rails Blog (Build 20100722155716)
by Jasmin Blanchette of Trolltech My favorite anecdote out of this is actually from Raymond Chen's MSDN blog about why the API call SHStripMneumonic is so heinously misspelled. Oops.Consuming APIs is something most developers–and even some non-developers–are doing most of the time.