Pages tagged rest:

Towards RESTful PHP - 5 Basic Tips | Kris Jordan
http://www.krisjordan.com/2008/12/02/towards-restful-php-5-basic-tips/

About PHP- Once read
Très bon
Writing Blazing Fast, Infinitely Scalable, Pure-WSGI Utilities - Die in a Fire - Eric Florenzano’s Blog
http://www.eflorenzano.com/blog/post/writing-blazing-fast-infinitely-scalable-pure-wsgi/
Create a REST API with PHP « Gen X Design | Ian Selby
http://www.gen-x-design.com/archives/create-a-rest-api-with-php/
One of the latest (sort of) crazes sweeping the net is APIs, more specifically those that leverage REST. It’s really no surprise either, as consuming REST APIs is so incredibly easy… in any language. It’s also incredibly easy to create them as you essentially use nothing more than an HTTP spec that has existed for ages. One of the few things that I give Rails credit for is its well thought-out REST support, both for providing and consuming these APIs (as its been explained by all the Rails fanboys I work with).
Ajaxian » Designing a JavaScript client for a REST API
http://ajaxian.com/archives/designing-a-javascript-client-for-a-rest-api
So you want to write a script that sites all over the web can use to access your REST API, eh? Well, that would be pretty straightforward if it weren’t for two things: 1. browser same-origin restrictions on XMLHttpRequests (XHRs) and inter-window/frame access 2. the lack of wide browser support for HTML 5-style message passing between windows. The Same-Origin Policy and its minor browser-specific variations are detailed elsewhere, so I’ll just summarize it with a few key points. I use the term window to mean window object, which can be a top-level page or reside inside a frame or iframe.
So you want to write a script that sites all over the web can use to access your REST API, eh? Well, that would be pretty straightforward...
A comprehensive article outlining an approach on how to create a RESTful JavaScript client. The article explains not only how to create a client for your own RESTful services, but also interacting with cross-domain ones. There is also code posted on Google Code which implements the concepts presented in the article.
Persevere: The JSON database and JavaScript application server
http://www.persvr.org/
RestfulX Framework
http://restfulx.github.com/
framework restfull para desarrollar aplicaciones flex
RESTful Flex Development
jespern / django-piston / wiki / Home — bitbucket.org
http://bitbucket.org/jespern/django-piston/wiki/Home
RESTful framework for Django
jespern / django-piston / wiki / Home — bitbucket.org
A tool for creating RESTful APIs in Django.
Get the latest version (0.1) here. A mini-framework for Django for creating RESTful APIs. Piston is a relatively small Django application that lets you create application programming interfaces (API) for your sites. It has several unique features: * Ties into Django's internal mechanisms. * Supports OAuth out of the box (as well as Basic/Digest or custom auth.) * Doesn't require tying to models, allowing arbitrary resources. * Speaks JSON, YAML, Python Pickle & XML (and HATEOAS.) * Ships with a convenient reusable library in Python * Respects and encourages proper use of HTTP (status codes, ...) * Has built in (optional) form validation (via Django), throttling, etc. * Stays out of your way. Piston logo NB: OAuth ships with piston for now, but you are not required to use it. It simply provides some boilerplate in case you want to use it later (consumer/token models, urls, etc.) Documentation o Piston Documentation + Gett
Mercurial hosting - we're here to serve.
REST worst practices
http://jacobian.org/writing/rest-worst-practices/
A few weeks ago, I sent the following in a email to a co-worker asking for input on designing REST APIs in Django. Since then, I’ve quoted myself a few times; I thought these thoughts would be worth a (slightly edited) public home. I think the best way to dive in terms of mistakes to avoid. If you poke around you’ll find a couple-three different stabs at writing a generic REST API module for Django. So, with no further ado, some REST “worst practices:”
REST worst practices
A few weeks ago, I sent the following in a email to a co-worker asking for input on designing REST APIs in Django. Since then, I’ve quoted myself a few times; I thought these thoughts would be worth a (slightly edited) public home. I think the best way to dive in terms of mistakes to avoid. If you poke around you’ll find a couple-three different stabs at writing a generic REST API module for Django. So, with no further ado, some REST “worst practices:” Conflating models and resources In the REST world, the resource is key, and it’s really tempting to simply look at a Django model and make a direct link between resources and models — one model, one resource. This fails, though, as soon as you need to provide any sort of aggregated resource, and it really fails with highly denormalized models. Think about a Superhero model: a single GET /heros/superman/ ought to return all his vital stats along with a list of related Power objects, a list of his related Friend objects, etc. So the dat
Best Practices for building JSON REST Web Services « Building Feedly
http://blog.feedly.com/2009/05/06/best-practices-for-building-json-rest-web-services/
A few of our friends have been asking us what are some of the best practices we learnt over the last two years designing and implementing RESTful Web Services as the back-end of the feedly service. Here is a quick/high level brain dump: Phase 1 – Defining a simple resource/service | Take a sample resource such as Customer Information, model it as JSON. Build a simple servlet where PUT creates a new customer, GET returns the customer information based on the customer key, DELETE deletes the customer and POST updates the customer information. Make sure that PUT returns the right information regarding the URL of the newly created resource. In our case, we have a framework which maps JSON to our Java Model and use hibernate to persist that model in a MySQL database. The important things for this phase are to the JSON representation right and the base url formatting simple and clean. Phase 2 – Implementing a client | Learn how to build a simple Javascript client which interacts with the s
- added by harper reed's google reader
Paul Dix Explains Nothing: Breath fire over HTTP in Ruby with Typhoeus
http://www.pauldix.net/2009/05/breath-fire-over-http-in-ruby-with-typhoeus.html
Might be a good alternative to Net/HTTP for Context Hero. How hard would it be to incorporate caching?
micha's resty at master - GitHub
http://github.com/micha/resty/tree/master
curl GET/POST/PUT/DELETE
rest from the command line (bash+curl)
Very, very cool. Fire up a local REST host pointing to any service, and then GET /blogs.json etc from the command line.
Little command line REST interface that you can use in pipelines. [Sublime :-) ]
resty is a RESTful HTTP friendly wrapper around curl
PUT or POST: The REST of the Story « Open Sourcery
http://jcalcote.wordpress.com/2008/10/16/put-or-post-the-rest-of-the-story/
Interesting explanation on why CRUD with REST doesn't directly map to the HTTP verbs POST, GET, PUT, and DELETE
Why CouchDB?
http://books.couchdb.org/relax/why-couchdb
man, I really really wish I understood this stuff.
shows
“Django may be built for the Web, but CouchDB is built of the Web. I’ve never seen software that so completely embraces the philosophies behind HTTP. CouchDB makes Django look old-school in the same way that Django makes ASP look outdated.”
ebook on why you would choose couchdb
Why REST ? | /var/log/mind
http://blog.dhananjaynene.com/2009/06/why-rest/
Putting Java to REST | Javalobby
http://java.dzone.com/articles/putting-java-rest
See comments to post for information about integrating security.
RED: <>
http://redbot.org/
RED (Resource Expert Droid) checks HTTP resources to see how they use HTTP, makes suggestions, and finds common protocol mistakes
Get Your API Right « Trek
http://wonderfullyflawed.com/2009/07/02/get-your-api-right/
If you’re not allowing clients to create new data, or update/delete existing data on your system then you do not have an API. You have a feed. There’s nothing wrong providing read-only access to your data (it’s laudable, in fact), but I’m often disappointed to hear “Yeah! We have an API” only to find the person really meant they offered a number of customizable data feeds as XML.
"I can’t stand working with a poorly designed API! If you’re about to design or release an API for the web and want to avoid the ire of your developers, I’ve summed up the best (and worst) of what I’ve seen into 8 rules..."
Controlando el API
8 key gotchas when implementing RESTful web APIs. great advice
If you’re about to design or release an API for the web and want to avoid the ire of your developers, I’ve summed up the best (and worst) of what I’ve seen into 8 rules:
mnot’s Web log: What to Look For in a HTTP Proxy/Cache
http://www.mnot.net/blog/2009/06/12/cache-win
How To Create An API? (10 Tutorials)
http://www.webresourcesdepot.com/how-to-create-an-api-10-tutorials/
API design tutorial
Free Web Resources Everyday - WebResourcesDepot
The Amazing Blog : Your Web Service Might Not Be RESTful If…
http://www.theamazingrando.com/blog/?p=107
added a single resource that described the locations of these other resources, they would have much more flexibility in the future. An example of the content of such a resource:
Good blog on the basics of building RESTful web services
http://news.ycombinator.com/item?id=713959
Getting Started With Restful Authentication in Rails - Nettuts+
http://net.tutsplus.com/tutorials/ruby/getting-started-with-restful-authentication-in-rails/
authlogic
InfoQ: RESTful HTTP in practice
http://www.infoq.com/articles/designing-restful-http-apps-roth
InfoQ: RESTful HTTP in practice - http://bit.ly/Zrqmk Great article but leaves out hypermedia side [http://bit.ly/UhPEK] completely. [from http://twitter.com/dhinchcliffe/statuses/3428371918]
hurl
http://hurl.r09.railsrumble.com/
Hurl makes HTTP requests. Enter a URL, set some headers, then view the response. Perfect for APIs.
Web app for testing HTTP requests.
online version of curl for viewing HTTP messages
Analyse HTTP headers. Like curl, but on the web.
Hurl makes HTTP requests. Enter a URL, set some headers, then view the response. Perfect for APIs.
Netflix API - Welcome to the Netflix Developer Network
http://developer.netflix.com/
Ruby, Rack and CouchDB = lots of awesomeness « Merbist
http://merbist.com/2009/07/27/ruby-rack-and-couchdb-lots-of-awesomeness/
"couchdb ruby"
Logging to couch
InfoQ: Tim Bray on the Future of the Web
http://www.infoq.com/interviews/tim-bray-future-of-web
RESTful Transactions « Open Sourcery
http://jcalcote.wordpress.com/2009/08/06/restful-transactions/
James Strachan's Blog: JAX-RS as the one Java web framework to rule them all?
http://macstrac.blogspot.com/2009/01/jax-rs-as-one-web-framework-to-rule.html
Jersey/JAX-RS, the ultimate java web framework?
The REST java spec and web apps
Orderly JSON
http://orderly-json.org/
Orderly is a textual format for describing JSON. Orderly can be compiled into JSONSchema. It is designed to be easy to read and write.
Orderly is a textual format for describing JSON. Orderly can be compiled into JSONSchema. It is designed to be easy to read and write. JSONSchema attempts to provide a representation for three distinct types of information about JSON structures: * Data structure (for documentation and validation purposes) * Storage attributes (information pertinent to tools that wish to persist JSON data) * Interaction Control (providing hints on how to render a UI where data can be manipulated). JSONSchema attempts to provide a representation for three distinct types of information about JSON structures: * Data structure (for documentation and validation purposes) * Storage attributes (information pertinent to tools that wish to persist JSON data) * Interaction Control (providing hints on how to render a UI where data can be manipulated).
Pragmatic Programming Techniques: RESTFul Design Patterns
http://horicky.blogspot.com/2009/05/restful-design-patterns.html
Summarize a set of RESTful design practices that I have used quite successfully.
Elastic Search - Open Source, Distributed, RESTful Search Engine
http://www.elasticsearch.com/
A distributed, highly available RESTful Search Engine based on Lucene
ElasticSearch is an open source, distributed, RESTful search engine built on top of Lucene.
ElasticSearch is an open source, distributed, RESTful, Search Engine.
An open source search engine built on top of Lucene that can be distributed across multiple indexes on different nodes.
justin / webmachine / wiki / BigHTTPGraph — bitbucket.org
http://bitbucket.org/justin/webmachine/wiki/BigHTTPGraph
http diagram v3
updated version of Alan Dean's diagram
http flowchart
Ruby Best Practices - Blog
http://blog.rubybestpractices.com/posts/gregory/rails_modularity_1.html
Sharing model data via ActiveResource -- good stuff.
Dare Obasanjo aka Carnage4Life - REST API Design: Invent Media Types, Not Protocols and Understand the Importance of Hyperlinks
http://www.25hoursaday.com/weblog/2008/10/24/RESTAPIDesignInventMediaTypesNotProtocolsAndUnderstandTheImportanceOfHyperlinks.aspx
The key thing to remember is that REST is about building software that scales to usage on the World Wide Web by being a good participant of the Web ecosystem. Ideally a RESTful API should be designed to be implementable by thousands of websites and consumed by hundreds of applications running on dozens of platforms with zero coupling between the client applications and the Web services. A great example of this is RSS/Atom feeds which happen to be one of the world's most successful RESTful API stories.
CouchDB with CouchRest in 5 minutes « The Merbist
http://merbist.com/2009/05/17/couchdb-with-couchrest-in-5-minutes/
The other night, during our monthly SDRuby meetup, lots of people were very interested in learning more about CouchDB and Ruby. I tried to show what Couch was all about but I didn’t have time to show how to use CouchDB with Ruby. Here is me trying to do that in 10 minutes or less. I’ll assume you don’t have CouchDB installed.
CouchDB with CouchRest in 5 minutes The other night, during our monthly SDRuby meetup, lots of people were very interested in learning more about CouchDB and Ruby. I tried to show what Couch was all about but I didn’t have time to show how to use CouchDB with Ruby. Here is me trying to do that in 10 minutes or less. I’ll assume you don’t have CouchDB installed.
Another take on content negotiation
http://www.b-list.org/weblog/2008/nov/29/multiresponse/
MultiRes
serve content based on client accept header. whatever user is asking for i.e. json or xml.
Richardson Maturity Model
http://martinfowler.com/articles/richardsonMaturityModel.html
Richardson Maturity Model : A staged approach towards RESTfulness by @martinfowler http://ff.im/-hUO5V
/via Leonard Richardson
A model (developed by Leonard Richardson) that breaks down the principal elements of a REST approach into three steps. These introduce resources, http verbs, and hypermedia controls.
Open Data (OData)
http://www.odata.org/
The simplest OData service can be implemented as simply as a static file that follows the OData ATOM or JSON payload conventions. For scenarios beyond static content, frameworks are available to help in creating OData services. See the OData developer page for additional information.
New open data protocol being pushed by Microsoft
REST for Java developers, Part 4: The future is RESTful - JavaWorld
http://www.javaworld.com/javaworld/jw-04-2009/jw-04-rest-series-4.html
Find out why REST interfaces are foundational for emerging architectures such as the Semantic Web. Brian Sletten takes a big-picture view of REST, now and in the future, in this final article in his series.
JavaWorld
Graph API - Facebook Developers
http://developers.facebook.com/docs/api
The new Graph API attempts to drastically simplify the way developers read and write data to Facebook.
https://graph.facebook.com/btaylor
Documentation de l'API pour récupérer les informations et les contacts des utilisateurs de Facebook.
Welcome | Twitter API Explorer - twitapi.com
http://twitapi.com/explore/
Simple Wins : Daytime Running Lights
http://jchrisa.net/drl/_design/sofa/_show/post/Simple-Wins
Background on jchrisa's Toast (standalone chat app in CouchDB+JS+HTML)
The point is to show how CouchDB's "databasey" features, because they are implemented using HTTP, can be leveraged to make powerful end-user experiences, with just a minimum of code.
Designing a RESTful Web Application - Quandy Factory
http://quandyfactory.com/blog/65/designing_a_restful_web_application
useful collection of thoughts
Google Storage for Developers - Google Code
http://code.google.com/apis/storage/
Got the Google Store invite: http://code.google.com/apis/storage - Need to find time to play with it...
Google Storage for Developers is a RESTful service for storing and accessing your data on Google's infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. Highlights include:
Rethinking Rails 3 Controllers and Routes | Free PeepCode Blog
http://blog.peepcode.com/tutorials/2010/rethinking-rails-3-routes
Clojure
Improving URL routing for web apps.