ADNKit
ADNKit copied to clipboard
joeldev
Streams API support
From berg: "before you go too far down the road on streaming API stuff, understand that it's not meant for client consumption (but there are different APIs comign soon for that...)"
May just wait until the APIs intended for client consumption go live. I'd rather not develop a whole component of the framework that I intend to throw out soon.
Has there been any more info on this from berg? I'm building something at the moment that would benefit greatly from Message streams (I think — I'm still getting my head around how this all pieces together).
It's something we're actively working on now -- hoping to build a proof-of-concept using ADNKit soon. :)
Thanks @berg! Is there any way to interact with Streams manually at this stage, or is it all still behind the curtain?
You can certainly consume streams on the server side, e.g., to hook them up to APNs. However, they are limited to app-wide usage only, and have significant state associated with turning them up and connecting to them, etc. There isn't a good way for you to consume a stream from an OS X or iOS app just yet.
Sounds like I'd be well served to wait for you guys to finish up before I start down this path.
@joeldev, should we put all of the calls to ADNKit which involve the semaphore on a serial queue (for user streams)?
Is there an ETA on this - building a new app now and would love to keep all ADN communication via ADNKit, but want to use the new streams!
It is currently being done on a branch (user-streams). You're welcome to check out that branch and try it out - we'd love feedback!
I've just checked out the user-streams branch, @joeldev but there's some odd dependencies in there (a customised version of SocketShuttle? It's using an init method that don't seem to exist…)
It's functioning (albeit not with much polish), but the bug I'm noticing right now is that after using a streaming-request (-requestStreamingUpdatesForOperation:), the operation queue seems to stop running operations, even though it's not suspended.
Somehow I get the sense it's related to my mutation of the request (which is not meant to be done.)
Guys, can I get a bit of direction as to what I feed into the AKNJSONRequestOperation parameter of -requestStreamingUpdateForOperation:withDelegate:? Not really sure how to get this to start streaming.
Supply a regular request that supports streaming, such as the user's current unified stream, into it. You'll get the regular endpoint response callback, as well as starting to receive streaming updates. As I said above, however, it will cause oddities with other requests that are performed down the line.
So no ETA at this point? Development on Dot for Mac starts today, and I'd like to use as soon as possible. Great work though guys, I really like what I see :)