Colin Deasy wrote:
Thanks for the info. I'll certainly look into the CFNetwork API. I
was really hoping for a nice solution to come about for the cocoa
API's but I've since given up hope and started using libcurl, which
is actually a really nice library to work with.
If CocoaAsyncSocket
On Nov 21, 2009, at 11:39 AM, Colin Deasy wrote:
> Hey,
>
> Thanks for the info. I'll certainly look into the CFNetwork API. I was really
> hoping for a nice solution to come about for the cocoa API's but I've since
> given up hope and started using libcurl, which is actually a really nice
>
> Subject: Re: NSRunloop + shared thread
> From: hank.l...@runbox.com
> Date: Fri, 20 Nov 2009 09:28:02 -0500
> CC: colde...@hotmail.com; cocoa-dev@lists.apple.com
> To: j...@mooseyard.com
>
> On Nov 19, 2009, at 7:51 PM, Jens Alfke wrote:
>
> > On Nov 19, 2009,
On Nov 19, 2009, at 7:51 PM, Jens Alfke wrote:
> On Nov 19, 2009, at 3:40 PM, Colin Deasy wrote:
>
>> This shared thread is actually handling potentially large numbers of
>> concurrent url connections/downloads. The reason that I want a block in some
>> of those at different times is a for a fo
On Nov 19, 2009, at 3:40 PM, Colin Deasy wrote:
> This shared thread is actually handling potentially large numbers of
> concurrent url connections/downloads. The reason that I want a block in some
> of those at different times is a for a form of bandwidth control I am trying
> to do.
I don't
On Thu, Nov 19, 2009 at 3:40 PM, Colin Deasy wrote:
> I see what you mean but at the moment Im finding it hard to see another
> avenue. To give a bit more detail on the situation. This shared thread is
> actually handling potentially large numbers of concurrent url
> connections/downloads. The
times is a for a form
of bandwidth control I am trying to do. I know I could do this by having a
separate thread for each task but there is quite a lot of overhead with that
and from the tests I have ran, it spins too much.
> Subject: Re: NSRunloop + shared thread
> From: j...@mooseyard.com
On Nov 19, 2009, at 2:54 PM, Colin Deasy wrote:
> I have a shared thread that is used to process multiple asynchronous tasks.
> But at some point, a task may need to 'pause' its execution, and cannot exit
> its method and wait to be re-called, how can I do this?
They're not really asynchronous
Hey,
I have a shared thread that is used to process multiple asynchronous tasks. But
at some point, a task may need to 'pause' its execution, and cannot exit its
method and wait to be re-called, how can I do this? In that method, where a
'pause' instance is brought about, can I use something li
