I'd like the ability to easily cancel requests too, not really sure if that's the job of the PAI or the Network Models though.

Ideally in this use case most of our requests should be cached, we could try having an API layer that insta-returns data synronously, then makes the network API call, updates the objects then does the async call. My gut impression is that this is how they do it in the tumblr app.

Another great feature would be:

• Don't emit a second network call, if a previous one for the same resource is already "in flight"

@orta best bet might be to separate networking layer from your persistence layer and use something like NSFetchResultsController for that binding goodness

I agree with both ( that's a smart one @shepting )

(Working on something here)

Closing, the responsibilities for this issue now lay in