Several months back, we announced SUP (Simple Update Protocol), a proposal for making RSS and Atom feed updates faster and more efficient. Since then, a number of services have added SUP support, we've SUP-enabled our feed fetcher, and there are now thousands of SUP enabled feeds being imported into FriendFeed. Among the services that now support SUP are Disqus, Brightkite, Identi.ca (and other La
(This is a write up of the talk that I gave at Velocity 2010 last Thursday. This is a joint work of myself, Nagendra Modadugu and Wan-Teh Chang.) The ‘S’ in HTTPS stands for ‘secure’ and the security is provided by SSL/TLS. SSL/TLS is a standard network protocol which is implemented in every browser and web server to provide confidentiality and integrity for HTTPS traffic. If there's one point tha
Hiroshi Nakamura - graph.facebook.comはSSL上でkeep-aliveさせてくれるのはいいが、タイムアウトの時のサーバからの切断処理がなんかおかしい。クライアント側でTCPのオプション指定しないといけないかも。まだ詳しく見てない。12:36 amDeleteUndo deleteReport spamNot spam Hiroshi Nakamura - buzz.google.comもSSL上でkeep-aliveさせてくれるし、切断も特に問題ない。が、graph（OAuth 2.0）と違ってOAuth 1.0aで、HTTP headerでのネゴが必要。おかげでクライアントがstatefulになり、マルチスレッドで共有してアクセスし放題、というわけにいかない（OAuth 2.0ならパラメータだから簡単）。結局リクエスト毎にクライアントを用意している。1
The WebSocket protocol has been touted as a great leap forward for bidirectional web applications like chat, promising a new era of simple Comet applications. Unfortunately there is no such thing as a silver bullet and this blog will walk through a simple chat room to see where WebSocket does and does not help with Comet applications. In a WebSocket world, there is even more need for frameworks li
Implementing PubSubHubbub subscriber support: A step-by-step guide One of the last things I did before leaving Plaxo was to implement PubSubHubbub (PuSH) subscriber support, so that any blogs which ping a PuSH hub will show up almost instantly in pulse after being published. It’s easy to do (you don’t even need a library!), and it significantly improves the user experience while simultaneously red
Abstract This document defines a lightweight, robust, and secure protocol for sending unsolicited notifications — especially comments and responses on syndicated feed content — to specified endpoints; along with rules to enable resulting content to itself be syndicated robustly and securely. This protocol defines the 'rules of the road' for these mechanisms, tying together and relying on lower lev
This is an older version of an Internet-Draft whose latest revision state is "Replaced". This document is an Internet-Draft (I-D). Anyone may submit an I-D to the IETF. This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process. Network Working Group I. Hickson Internet-Draft Google, Inc. Intended status: Standards Track February 4, 2010 Expires: August 8, 2010 T
_ 続ACIDからBASE 以前、acmqueueのBASEに関する記事の前半だけを勝手翻訳したが、続きをwinplusさんが翻訳してくれた。 実のところ、2フェーズコミットという技術は早すぎた自動化だと思う。えらく大層なことと複雑な仕組みではあるけれど、さっきまでオンラインだったシステムは直後もオンラインだろうという程度のあやふやな確信に頼って自動化しているだけのものだ。 よく似たシステムに、同時期にでてきたRPC（ORPCもそうだ）がある。 前提が高信頼性が確保できるクリーンルーム内の複数のノードから構成された分散システムだとしか思えない。それにしてもマシンは落ちるしネットワークは切れる。2フェーズコミットは、絶対に通信が可能だということと相手のプロセス（マシン）が落ちないことを前提としたシステムだという矛盾がある。SYNに対するACKを2時間待ってしまえばすでに成り立たないのだ。 早
Since the day in 2006 that our dialogue took place with an imaginary eBay Architect, he has been promoted to imaginary Enterprise Architect in an investment bank! Convinced by the merits of REST, he took his enthusiasm for it into his new job and embarked on architecting a trading system using REST or ROA as an alternative to SOA. Now, he hit upon a snag: he had a REST "bank server" generating bid
Specifications: W3C Recommendations: JSON Activity Streams 2.0 and Activity Vocabulary (current W3C Social WG publications) JSON Activity Streams 1.0 (2011) Activity Base Schema Audience Targeting for JSON Activity Streams Responses for Activity Streams Draft: Verb Definitions for Activity Streams Draft: Priority Extension for Activity Streams Atom Activity Streams 1.0 Community: Join the mailing
ptth (Reverse HTTP) implementation in a browser using Long Poll COMET ptth is an idea I have planning on implementing for a few years now. The basic idea is that you take normal HTTP semantics and reverse them, meaning that the client (from the TCP perspective) acts like a server (from the application perspective), and the server (from the TCP perspective) acts like a client (from the application
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
WaveSandbox.com: Federate This