To the best of my knowledge, running on a separate thread in configd
is fine. It is no different from running stuff on a separate thread in
any other process. All of the System Configuration APIs will handle
this without an issue. As with any other time you run in another
thread, it's similar to running in a separate process except that
there is slightly less overhead and if anything goes wrong, your code
can take out all of configd. The system won't recover well from that.
-josh
On Apr 18, 2008, at 2:34 PM, Mark Thomas wrote:
Hi All,
I'm looking to move all of my IOKit and System Configuration call's
off
the main thread, and onto a separate thread which I think should be
safe, as
I'm not sharing objects between thread's or trying to do re-entrants
call's,
so the code is running on another thread exactly same as did before
but just
not on the main thread.
I have already switched the code and it seems to work fine, I can
easily
control which modules are threaded, but I thought I ask here if there
something that I might have missed ?, or waiting to bite me ? Maybe
which
OS's I should only enable threading from ?, or is there main thread
dependency there ?
Thanks
Mark.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
