> And a third case which we're not entirely sure exists, but if it it does it'd > be nice to keep supporting it: > > 3) near-real-time delivery of an individual user's messages to a dedicated > microblogging client (extra Atom stuff is probably what the client wants to > consume, as that's the data they'd otherwise be polling for in the HTTP API) >
This is what we're interested in, our client understands the current StatusNet format as well as some others. > > If case 3) has some good real implementations, then it would be great to be > able to push the Atom data out only when it's actually going to be used. An > extra 4k isn't too awful for a desktop chat client in real-time, but can > really add up if you have offline delivery. > This is what we've been building over the last year, pics here; http://is.gd/bP9h2 I may as well let the cat out of the bag, go grab the 'beta' here, we're announcing next week. :) http://esm.cleartext.net/esm/ Note: No discovery or group chat in this release, but auto-update is enabled. > In both cases, I'd want to make sure that if we do discovery/detection that > the receivers that need Atom will actually respond appropriately! Is anything > currently deployed that already does this without tying into pubsub, which > isn't used by what we've currently got? > > -- brion vibber (brion @ status.net)
