Cool ! Bret and I met on Friday and agreed on the minimal changes needed to support arbitrary formats in PubSubHubbub
I will post what we discussed on the wiki in detail but its pretty straightforward just using HTTP Headers Web Linking for hub and topic url and Date header for update date. On Sat, Jun 5, 2010 at 2:34 PM, Matthew Terenzio <[email protected]>wrote: > Very cool. I didn't read it word for word yet, but I like the direction. > > > On Sat, Jun 5, 2010 at 3:33 PM, Martin Atkins <[email protected]>wrote: > >> >> Hi all, >> >> Today I wrote up a first draft for a variation on PubSubHubbub for >> JSON-based applications: >> >> http://martin.atkins.me.uk/specs/pubsubhubbub-json >> >> As noted in the specification document, the goal is to make the hub as >> dumb as possible, having the payloads just be opaque JSON objects as far as >> the hub is concerned. This means that this can be used for multiple >> JSON-based applications without changing the hub. >> >> The near-term goal is to allow the fledgling "Activity Streams API" spec >> to use this as a transport, but I also want to make it useful for delivering >> other content and for proprietary payloads like those used in Facebook's >> real-time notifications API. >> >> It'd be nice if this format could be supported alongside Atom and RSS in >> the App Engine hub reference implementation, though I've not yet dug deeply >> into the code to figure out how hard that might be. >> >> >> >> >
