No, actually I've completely missed that it was answered. Thank you. Unfortunatelly, the requester is expecting a return data, error or a redirect. And until the api can be respeced, the sync response has to stay in. It isn't that it needs to load from network every request, but some volotile data does have to check the server to pull down the changes before serving the data.
I will try to offload the server access to a different thread (though I still need to block the protocol thread because I still have to return the correct data for the current call). but now I'm also curiouse of what you mewant by posting a block to another dispatch queue ? On Thu, Sep 6, 2012 at 7:55 AM, Jean Suisse <jean.li...@gmail.com> wrote: > Hi, > > Fritz Anderson is right. We can only agree. > And recently, they made following Jens Alfke's advice incredibly easy. > Just post a block to one of the available dispatch queues (not the one > running on your main thread thought) and let it run its curse. > > Jean > > On 6 sept. 2012, at 16:36, Fritz Anderson wrote: > > > From what Google tells me, you got a prompt response from Jens Alfke, a > very experienced Cocoa-networking programmer, explaining why what you're > doing shouldn't be expected to work. Are you looking for a workaround, or > just for somebody who will give you better news? I don't think better news > is in the cards. > > > On 29 août 2012, at 22:58, Jens Alfke wrote: > > > If you must use a synchronous API, spawn a new thread to run it on. > > > > > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
