Road Map
Alex Chaffee
Emmanuel and I have been chatting off-list about this. Here's our
current thoughts.
On Sat, Nov 12, 2011 at 5:48 AM, Emmanuel Pire <pirem...@gmail.com> wrote:
> So we would keep hosting at lipsumarium until Ruby code is ready. But then
> what code will post to lipsumarium ? I'm not sure i get it. or do you speak
> about a temporary bridge that only replicate queries to lipsumarium, so
> later you can just handle it yourself ? would be fine to me.
Basically, yes. I see the steps as:
1. create "GET sharebro.org/feed/12345" that reads
"http://lipsumarium.com/greader/feed?_USER_ID=12345"
and re-sends it verbatim
2. create "POST sharebro.org/feed/12345" that sends its
parameters to the lipsum site behind the scenes
3. change the JS to post to the new feed (same as the old feed,
different URL) and get people to subscribe to the new stable feed URL.
4. Write a clean, Ruby, test-driven feed posting and serving system on
sharebro.org
-- basically fill out the GET and POST endpoints I just described,
porting Em's PHP
4a. just before #5, seed the new feeds with all the items from the old feeds
5. switch the server-side code so new posts/fetches come from the new
DB rather than the old DB
In short --
1. make the client point to the new URLs that still work on the old server
2. wait a few days for propagating the new client JS
3. silent switchover
It's the same sort of phased rollout strategy I've used at
clients-not-to-be-mentioned (but trust me they know how to deploy).
== Finally getting your friends back inside Reader
I'm investigating two options:
OPML - this would be easy but I'm worried about the import -- how hard
would it be to re-import if something changes, say if the source of
the feed moves
Google Reader API - like what Ridllr does but with better names for
feeds (not just their big user ids) and your ability to pick and
choose *which* of your friends' feeds to subscribe to, e.g. their G+
Posts
--
Alex Chaffee - al...@stinky.com
http://alexchaffee.com
http://twitter.com/alexch