PUBLIC MARKS with search r.i.c.e.(rest,ice,compression,andelevation)

karl Says:

novembre 28th, 2009 at 10:15

REST est un style architectural qui est encore une couche au dessus de HTTP.

Je rejoins Christian dans son analyse. Chacun des domaines est d’ailleurs interprété en fonction de la culture propre des intervenants. Lorsque l’on SPDY de Google qui est une forme d’extension à HTTP. Ils ne s’intéressent proprement dit qu’à l’efficacité du transport et pratiquement pas à l’amélioration du transfert.

Google centralise tous les services dans une même coquille. Sa seule interaction au final n’est avec qu’avec les logiciels clients. L’interopérabilité avec les autres serveurs n’est presque pas un objectif à terme. Ils ont besoin de rapidité, ils ont des besoins spécifiques qu’ils maîtrisent au cœur de leurs applications. Lorsqu’on a créé un écosystème avec un fort contrôle sur tous les éléments du système, on peut se permettre d’imposer sa loi à l’écosystème. Microsoft l’a fait dans l’univers de la bureautique. Google le fait petit à petit pour le Web. Nous n’y sommes pas encore bien sûr.

Pour Google, le transfert n’est pas important ou plutôt il est si peu mis en pratique (quid de HTTP PUT, DELETE, etc., des mime types et des headers) sur le Web aujourd’hui, que Google peut se concentrer sur ce qui améliore le transport des données.

Recently InfoQ did a good summary of the debates around the apparent (to some) limitations of REST when it comes to creating good Web services. At issue is that REST APIs seem to expose "CRUDy" services that fly in the face of years of good services design, particularly when they are just read/write interfaces instead of the richer, full REST architecture (more on what this is later.) The discussion was spurred by Arnon Rotem-Gal-Oz's assertion recently that CRUD is bad for REST, which in my opinion is close but not quite right.

Today we'd like to share with the web community information about SPDY, pronounced "SPeeDY", an early-stage research project that is part of our effort to make the web faster. SPDY is at its core an application-layer protocol for transporting content over the web. It is designed specifically for minimizing latency through features such as multiplexed streams, request prioritization and HTTP header compression.

GeoREST is a framework for accessing, distributing, and editing raw geospatial data over the web. Because it is based on REST, it supports searching using standard Web search engines such as Google and Bing.

you said: “Especially given the by-now-clichéd recognition that we’ve decisively become an urban species”

It is indeed very interesting to think about urban systems design given there was a major move toward cities. That said I have the feeling that this move comes with, at least, three issues:

1. access to the “thought” urban environment,

2. the space left where 50% of the population is still living,

3. the space of this growth

There are many areas in the world where the growth of the cities is made by people without access or a limited access to the thought urban environment. Poor people living in slums or just in a space which is not part of the work of urban planner per say. In a recent exhibition about slums I went, it was very interesting to see that the organic structure of the slums was making possible for the individuals to create a rich and meaningful space, driving sometimes to less criminality than more traditional areas of the city. The slum is a forced collective creative space for survival.

The rest of the population, the 50% living in deserted areas are the forgotten of this story. It’s indeed more “fun”, interesting for researchers, sociologists to observe and think about the density in urban space (richness of interactions) more than the low level of activities in the “countryside”. Though there are equal challenges there in terms of design and space organization, access to services, etc.

Finally, is it really cities which are growing? What we call urban space often relates to the city center, but I have the feeling that the growth is happening in the in-between space (suburbs), which is again a complete disaster in terms of design, even more so in rich countries. The private space is becoming a space of non-creativity, dead areas of non activities. Someone, who wants to start a small business in between two buildings on the grass of a random suburb of a rich city, will not last for very long. Complete different dynamic than the slum where unregulated areas give the opportunity of creative solutions for surviving or living.

remoteobjects are real subclassable Python objects on which you can build a rich API library. remoteobjects provides easy coding and transfer between Python objects and a JSON REST API. You can define the resources in a RESTful API as `RemoteObject` classes and their properties. These objects then support using the basic HTTP verbs to request and submit data to the API.

A RESTful, hypertext-driven system needs to enable clients to create a new resource that depends on three or more resources of different types. What's the best method to expose this capability?

API designers, please note the following rules before calling your creation a REST API:

Amazon's S3 is a nice and cheap way to have a remote backup system. But it is REST based which make it not very easy to use. This project just add the normal file system semantic to it.

Today, the sexuality is a taboo for elderly generations.

During my investigation, I have observed many prejudices about this topic in our society.

However, sexuality is always active over 70 years old.

I have revaled three specifics aims to start my project :

- Stimulate Sexual desire of elders into rest-home

- Educate practical nurses and students

- Sensitize general public about sexuality of elderly people

You can watch the differents ideas I suggested

to resolve these 3 problems in Diploma's part.