Re: NSURLConnection not reentrant?
Re: NSURLConnection not reentrant?
- Subject: Re: NSURLConnection not reentrant?
- From: Ed Voas <email@hidden>
- Date: Mon, 21 Nov 2005 23:22:20 -0800
Because the caller has asked to do a sync fetch of something in their
completion routine. We're running a javascript engine over all this
and in someone's completion routine (for example, in their callback
to XMLHttpRequest, they fetch something implicitly, but we do it sync
(in this case we are reloading an image and we *have* to do it sync
because they've requested an attribute of the image we need to
reload... it's a lazy fetch). On Windows I use a thread and we post
the results to a completion queue. Mac does basically the same thing
under the covers, but apparently whilst it is calling is completion
procs, it doesn't allow any other requests to report back to their
delegates or something. I would like it better if it behaved more
like timers... a timer can start another invocation of the run loop
and other timers will fire, but the original timer will not fire
again until it's exited. This seems like it stops ALL procs from
being called. Not just the one you are in.
On Nov 21, 2005, at 10:54 PM, John C. Randolph wrote:
On Nov 21, 2005, at 4:22 PM, Ed Voas wrote:
The trick is, we have to do it 'synchronously' so we end up not
leaving the current invocation of the run loop.
Why?
-jcr
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden