Home
sven duzont's Library tagged → View Popular
10 Jul 09
ongoing · Slow REST
We’re working on a fairly substantial revision of the Sun Cloud API, motivated by this problem: In a RESTful context, how do you handle state-changing operations (POST, PUT, DELETE) which have substantial and unpredictable latency?
26 Mar 09
Paper tigers and hidden dragons » Untangled
-
The solution, which I mentioned briefly at the talk, is to provide a resource that reflects all of the changes on Flickr during a given time period. Anyone (not just FriendFeed) can perform a GET on that resource to find out what has changed. In fact, one such example is the SUP (Simple Update Protocol) just introduced by FriendFeed. However, I had something more efficient in mind.
-
Instead of a list of changed user ids or URIs, we can represent the state as a sparse bit array corresponding to all of Flickr’s users. I don’t know exactly how many users there are at Flickr, but let’s be generous and estimate it at one million. One million bits seems like a lot, but it is only 122kB in an uncompressed array. Considering that this array will only contain 1s when an update has occurred within the last minute, my guess is that it would average under 1kB per representation.
Selected Tags
Related Tags
Sponsored Links
Ads by Google
Top Contributors
Groups interested in rest
Related Lists on Diigo
-
diigo v3 review
The entire Diigo team is pl...
Items: 39 | Visits: 2282
Created by: Vincent Tsao
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo