ReverseHttp
http://www.reversehttp.net/index.html

Tunnel HTTP over HTTP, in a structured, controllable, securable way. Let programs claim part of URL space, and serve HTTP, all by using an ordinary HTTP client library.

An interesting alternative to polling http services.

not polling

Interesting web hooks stuff. Yet another PubSub solution: http://reversehttp.net/

singpolyma: Interesting web hooks stuff. Yet another PubSub solution: http://reversehttp.net/

pubsub appengine atom http webhooks

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

A simple but clever way of using web hooks (HTTP callbacks) to inform subscribers that an Atom feed has updated in almost real-time.

A simple, open, web-hook-based pubsub protocol & open source reference implementation.

Une architecture distribuée de Pub/Sub avec HTTP

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.

Convinced from spending hours reading rave reviews, Bob eagerly clicked "Proceed to Checkout" for his gallon of Tuscan Whole Milk and... Whoa! What just happened?

RED (Resource Expert Droid) checks HTTP resources to see how they use HTTP, makes suggestions, and finds common protocol mistakes

InfoQ: The First Few Milliseconds of an HTTPS Connection

リアルタイム性

分かりやすい日本語の解説。

** Posted using Viigo: Mobile RSS, Sports, Current Events and more **

Back in the day you could, given somebody's UNIX account (email address), type finger email@example.com and get some information about that person, whatever they wanted to share: perhaps their office location, phone number, URL, current activities, etc. The finger protocol, sadly, died. Fast-forward to Web 2.0. We're currently bickering about how we do interop between all these social web services, and even how we represent a person's identity. The two main identity identifier camps are email addresses and URLs.

Google Code Project Page for "WebFinger" protocol

We're bringing back the finger protocol, but using HTTP this time.

from here, it should be downhill to world-wide, usable identity

WebFinger is about making email addresses more valuable, by letting people attach public metadata to them

math humor

When a guy goes into the bathroom, which urinal does he pick? Most guys are familiar with the International Choice of Urinal Protocol. It’s discussed at length elsewhere, but the basic premise is that the first guy picks an end urinal, and every subsequent guy chooses the urinal which puts him furthest from anyone else peeing. At least one buffer urinal is required between any two guys or Awkwardness ensues.

Seems that most still believe Google Wave primarily uses XMPP to pass data around. Turns out, XMPP is only used for server to server federation. Joe Gregorio has a good overview of the actual APIs and protocols used in Wave, but I still found it easier to create a diagram

"If Google is serious about Wave replacing [everything], the client-server protocol has to be properly worked out." http://bit.ly/Ey0SR

Not just XMPP = that is server to server

Real-Time Web Protocol PubSubHubbub Explained http://ff.im/-8TvlK [from http://twitter.com/kenmat/statuses/4462891327]

Mer om realtidswebben och pubsubhubbub-protokollet.

Notes on methods to eliminate corruption in a system by making honesty the most advantageous course of action

"Here’s a self-enforcing protocol for determining property tax: the homeowner decides the value of the property and calculates the resultant tax, and the government can either accept the tax or buy the home for that price. Sounds unrealistic, but the Greek government implemented exactly that system for the taxation of antiquities. It was the easiest way to motivate people to accurately report the value of antiquities."

@kasthomas: "SPDY, Google's answer to HTTP http://3.ly/Qbp" (from http://twitter.com/kasthomas/status/5693351096)

Home of the Chromium Open Source Project

A new protocol designed to provide better performance than http

A new experimental protocol to improve HTTP.

SPDY, pronounced "SPeeDY", is 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.

A Google a HTTP lecserélésén ügyködik

SPDY, [...] an early-stage research project that is part of our effort to make the web faster.

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.

Now Google wants to replace HTTP for the common good?

BERT and BERT-RPC are an attempt to specify a flexible binary serialization and RPC protocol that are compatible with the philosophies of dynamic languages such as Ruby, Python, PERL, JavaScript, Erlang, Lua, etc. BERT aims to be as simple as possible while maintaining support for the advanced data types we have come to know and love. BERT-RPC is designed to work seamlessly within a dynamic/agile development workflow. The BERT-RPC philosophy is to eliminate extraneous type checking, IDL specification, and code generation. This frees the developer to actually get things done.

"BERT and BERT-RPC are an attempt to specify a flexible binary serialization and RPC protocol that are compatible with the philosophies of dynamic languages such as Ruby, Python, PERL, JavaScript, Erlang, Lua, etc. BERT aims to be as simple as possible while maintaining support for the advanced data types we have come to know and love. BERT-RPC is designed to work seamlessly within a dynamic/agile development workflow. The BERT-RPC philosophy is to eliminate extraneous type checking, IDL specification, and code generation. This frees the developer to actually get things done."

The GitTorrent Protocol (GTP) is a protocol for collaborative git repository distribution across the Internet.

It might currently come across as a solution looking for a problem - and as one smart-ass with admin rights to the Google Code project reminds you on the source tab, "more alpha than the greek letter". The initial motivation was performance of downloads and in particular reducing load on kernel.org.

This could be interesting.

Why the NMEA standard is so much trouble

Away back in the dark and backward abysm of time when GPS technology was first being made generally available (e.g., 1993), only military-grade receivers were sensitive enough to use it where there were things like buildings and trees partly blocking the sky view. The first civilian customers to actually find a use for it were people messing about in boats. Thus it came to pass that the manufacturers of marine navigation systems were the first civilians to grapple with the question of how a GPS receiver should report TPV information over a wire to a navigational computer.

「PubSubHubbub」（パブサブハブバブ）という奇妙な名前のプロトコルが注目だ。2009年8月5日にグーグルはRSSリーダーサービスのGoogle ReaderでPubSubHubbub対応を明らかにしたほか、国内ではライブドアが、同じくRSSリーダー「livedoor Reader」とブログサービスの「livedoor Blog」でPubSubHubbubに初対応したことを8月18日に発表している。まだ対応サービスは少なく、その“効能”も「ブログの更新がRSSリーダーに反映されるのが、ほぼリアルタイムになりました」というだけで小さく見えるかもしれない。しかしPubSubHubbubは、ネット全体のリアルタイムコミュニケーションプラットフォーム化を促す重要なキーとなるかもしれない。

Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Ftsunami-udp.sourceforge.net

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

Every OAuth provider should encapsulate OAuth authorization inside OpenID. Better UX, lesser redirects http://bit.ly/7qbfPB

OAuth-enabled APIs su

http 方向返回

what's difference between comet and reverse http

RT @RobCottingham: Damned if I can figure out how to feed it an argument. But grooving on the idea behind OpenLike http://openlike.org

[openlike][facebook]

RT @kanter: checking out open like code http://openlike.org/

OExchange is an open protocol for sharing any URL with any service on the web.

Protocollo sharing

OExchange is an open protocol for sharing any URL with any service on the web.

OExchange

An open protocol for sharing any URL with any service on the web.