VertexDB is a high performance graph database server that supports automatic garbage collection. It uses the HTTP protocol for requests and JSON for it's response data format and the API is inspired by the FUSE filesystem API plus a few extra methods for queries and queues. It's implementation is currently built on top of TokyoCabinet and libevent.

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.

As updates and content flow in real time around the Web, conversations around the content are becoming increasingly fragmented into individual silos. Salmon aims to define a standard protocol for comments and annotations to swim upstream to original update sources -- and spawn more commentary in a virtuous cycle. It's open, decentralized, abuse resistant, and user centric.

answer Right. And it results in a type of error that doesn't teach you anything. You have chaotic errors where all you can say is, "Boy, this was really screwed up, and I guess I need to go in and go through the whole thing and fix it." You don't have errors that are proportionate to the source of the error. And that means you can never have any sense of gradual evolution or approximate systems. So, the real difference between the current idea of software, which is protocol adherence, and the idea I'm discussing, pattern recognition, has to do with the kinds of errors we're creating. We need a system in which errors are more often proportional to the source of the error.

This API defines a language- and platform- neutral protocol for Consumers to request address book, profile, and friends-list information from Service Providers. As a protocol, it is intended to be easy to understand and implement, either as a Service Provider or Consumer, using any language or platform of choice. It is also intended to be implemented by both individuals and small services as well as large providers, in any case where a service contains data about who a user knows and wishes to make that information portable, under the user's control.

This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.

A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom (and RSS).

Fabric is a Python library and command-line tool designed to streamline deploying applications or performing system administration tasks via the SSH protocol. It provides tools for running arbitrary shell commands (either as a normal login user, or via sudo), uploading and downloading files, and so forth.

>Les sites web ont été imaginés pour stocker des informations et les afficher à travers des navigateurs.

La prémice de départ est fausse et donc l’ensemble du billet. Le Web repose sur deux éléments essentiels : URI (identifier) et HTTP (protocol). La métaphore du Web est la gestion d’un espace d’information. Je n’ai rien nommé de physique encore et je n’ai pas parlé de contenu.

HTTP est une boîte à outils pour gérer des ressources avec des identifiants dans un espace d’informations et de placer une représentation possible de ces ressources.

Un site Web est une chose non définie de façon absolue. Cela peut-être une simple ressource dénotée par une seule URI. Cela peut-être l’ensemble des URIs sous un même domaine ou distribué sur plusieurs domaines, etc. Il n’y a pas de définitions cohérentes d’un site Web.

En revanche, il y a des délégations d’autorité gérées par HTTP pour chaque URI.

“Le Web” n’a jamais été égal à “sites Web”.

Je recommande la lecture de http://www.w3.org/DesignIssues/

The easiest way to understand how extensions work in Wave is to build a Wave robot. Robots are applications that interact with a Wave through the Wave protocol (HTTP interface). Currently, we only support robots hosted with Google App Engine. In the future, we will support any client architecture that implements the Wave protocol.

What makes portions of the Wave API opaque is the parts where the developers gave into temptation and serialized internal state (inside-out) vs designing an API (outside-in).

MOAI is a platform for aggregating content from different sources, and publishing it through the Open Archive Initiatives protocol for metadata harvesting. It’s been built for academic institutional repositories dealing with relational metadata and asset files.