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

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).

Microsoft is so often the behemoth everyone loves to hate that people overlook the stuff it does right. We tried its newer Web services and found five gems.

The AWS Toolkit for Eclipse is a plug-in for the Eclipse Java IDE that makes it easier for developers to develop, deploy, and debug Java applications using Amazon Web Services. With the AWS Toolkit for Eclipse, you’ll be able to get started faster and be more productive when building AWS applications.

Because this is just too cool!

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.

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

just use http already. don't invent your own wire format!

Why HTTP? The world doesn’t need another arbitrary binary protocol. Just use HTTP. Your life will be simpler. Originally this came up when scaling a gaggle of MySQL machines. I would have killed for a reliable proxy. It’s with this in mind that I’ve come up with my list of things that HTTP has that an arbitrary protocol will have to rebuild. Anytime you choose to use a service based on a non-HTTP protocol, look over this list and think carefully about what you’re giving up.

I like how this posts list out some of the great reasons to just use HTTP and the method of interop communication. So much is already built on HTTP and there are more than enough great tools ubiquitously available for interacting and communication over HTTP. The post also has a long discussion thread.

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

テストツールのまとめ

The Yahoo! Query Language lets you query, filter, and join data across any web data source or service on the web. Using our YQL web service, apps run faster with fewer lines of code and a smaller network footprint. YQL uses a SQL-like language because it is a familiar and intuitive method for developers to access data. YQL treats the entire web as a source of table data, enabling developers to select * from Internet.

YQL + Linked Data = possibilities

Execute elements run server-side JavaScript with E4X (na

php amazon aws tutorial s3

While Amazon Web Services (AWS) may seem like an unusual service for an online retailer, AWS is actually a natural progression for a company as seasoned at providing rock-solid internet applications as Amazon. Over the years, Amazon has cultivated a tremendous amount of knowledge around what it takes to build and maintain a successful, highly scalable web application. Fortunately for the rest of us, they've made this knowledge available to all developers via AWS.

So Amazon will be in the web services business for the foreseeable future. Now that we've established that learning more about AWS is not a risky investment of time, let's focus on Amazon's Infrastructure Services -- EC2, Amazon S3, SQS, SDB and EBS -- that make up the core of what some within AWS refer to as "undifferentiated heavy lifting." All of these services are available via both REST and SOAP interfaces. (We'll touch on both in this article, but we'll concentrate on the REST and REST-like Query approaches. ) A growing number of language specific toolkits are available for these services, so you can feel comfortable basing an architecture on AWS given its language-agnostic foundation. The knowledge that you can ramp up 200 servers in five minutes if you need them may be a liberating experience for you -- in the days before AWS, system architects had to worry about handling rapid scale with "hot spares" and other expensive on-hand capacity that often sat idle until the day...

Government Data in XML (web services etc)

More datasets courtesy of uncle Sam.

Listado de direcciones del gobierno de EEUU con WebServices que permiten acceder a informacion publica

See comments to post for information about integrating security.

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:

programar sin teclear

Para probar alg´un dia

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

Resources on using the official GitHub API. This site contains documentation on the major API sections and libraries you can use to make use of GitHub with your programs and scripts.

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]

If you're still struggling to understand how you might use Google Wave despite our in-depth first look, this quick video offers an excellent explanation of just one use case for how Wave can outshine email as a collaboration tool.

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business. Amazon RDS gives you access to the full capabilities of a familiar MySQL database. This means the code, applications, and tools you already use today with your existing MySQL databases work seamlessly with Amazon RDS. Amazon RDS automatically patches the database software and backs up your database, storing the backups for a user-defined retention period. You also benefit from the flexibility of being able to scale the compute resources or storage capacity associated with your relational database instance via a single API call. As with all Amazon Web Services, there are no up-front investments required, and you pay only for the resources you use.

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business.MySQL

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business. Amazon RDS gives you access to the full capabilities of a familiar MySQL database.

Tornado: Facebook's Real-Time Web Framework for Python

Possible to build a site like FB.. using Tornado Cassandra, Hive (hadoop underneath) memcache, Scribe, Thrift.

Real-time updates have become an important aspect of the social Web that make it easier to share with friends. In March, we introduced a real-time News Feed to make the stream as relevant and engaging as possible for users. Similarly, FriendFeed, which we recently acquired, built their entire site to support real-time updates. It hasn't been easy to build and scale these features, so today we're open-sourcing a core piece of infrastructure called Tornado, which was originally developed by the FriendFeed team. Tornado is a relatively simple, non-blocking Web server framework written in Python, designed to handle thousands of simultaneous connections, making it ideal for real-time Web services. Tornado is a core piece of infrastructure that powers FriendFeed's real-time functionality, which we plan to actively maintain. While Tornado is similar to existing Web-frameworks in Python (Django, Google's webapp, web.py), it focuses on speed and handling large amounts of simultaneous traffic.

starting point for ressources about Tornado python based webserver and tools

You should care because webhooks will be ubiquitous. You should care because they’re going to reshape the internet. You should care because webhooks are the next step in the evolution of communication on the internet and nothing will be left untouched.

"Webhooks are user-defined HTTP callbacks. Here’s a common example: You go to github. There’s a textbox for their code post webhook. You drop in a URL. Now when you post your code to github, github will HTTP POST to your chosen URL with details about the code post. There is no simpler way to allow open ended integration with arbitrary web services. -- You should care because webhooks will be ubiquitous. You should care because they’re going to reshape the internet. You should care because webhooks are the next step in the evolution of communication on the internet and nothing will be left untouched." -- Timothy Fitz

A tool to test webservices.

STORM is a free and open source tool for testing web services.

Jersey/JAX-RS, the ultimate java web framework?

The REST java spec and web apps

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.

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.

A new iPhone application which just debuted in Japan's App Store transforms the handheld into a full-blown web server.

When those Apple advertisements tout

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

天气预报接口 ruby on rails

Want to retrieve weather conditions in your Ruby script / application? There are four great solutions: WeatherMan, RWeather, rubyweather, and the Yahoo Weather Ruby API.

howto

Open source web services such as blogs, photo galleries, or mixtape services. How to install them and which services that RWW run on our own domains.

on demand video encoder with api

Hosted video encoding service.