Re: [2/3 solved] CFMessage woe - was: CFNotificationCenter ./. NSNotificationCenter
Re: [2/3 solved] CFMessage woe - was: CFNotificationCenter ./. NSNotificationCenter
- Subject: Re: [2/3 solved] CFMessage woe - was: CFNotificationCenter ./. NSNotificationCenter
- From: Iceberg-Dev <email@hidden>
- Date: Tue, 2 Mar 2010 09:00:19 +0100
On Mar 2, 2010, at 2:16 AM, Hado Hein wrote:
Iceberg-Dev <email@hidden> wrote:
To communicate between 2 threads, you can use Message Port for
instance, they work reliably.
Thanks,
I heard your warnings and moved my code to use CFMessage APIs. They're
doing what I want - and that works. Unfortunately I feel a bit lost
with
one special part of the implementation of the neccessary callbacks for
the listening port.
I get correct data with wrong CFTypeRefs in my Callback; perhaps
one can
shed some mileage one this.
It's not the same CFDataRef because:
1) the communication process is not local to the application.
2) CFMessagePort relies on Mach port which has no idea what a
CFDataRef is. It's only the CFMessagePort wrapping around Mach port
which is aware of the CFDataRef "struct".
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden