[Q] Comparison of Asynchronous handling of incoming data using "Descriptor Sources" in GCD and NSStream's Run-Loop scheduling?
[Q] Comparison of Asynchronous handling of incoming data using "Descriptor Sources" in GCD and NSStream's Run-Loop scheduling?
- Subject: [Q] Comparison of Asynchronous handling of incoming data using "Descriptor Sources" in GCD and NSStream's Run-Loop scheduling?
- From: JongAm Park <email@hidden>
- Date: Mon, 15 Oct 2012 09:20:10 -0700
Hello,
May I ask if there is some rationale in choosing these two asynchronous handling of incoming data? : Descriptor Sources in GCD and Run-Loop scheduling of NSStream.
It looks to me that the model between Run-Loop Scheduling and the approach using Descriptor Sources are very similar in the asynchronous fashion.
I have used Run-Loop scheduling in my previous projects, but would like to consider GCD. But would like to know what are pros and cons between them.
Surely, GCD is expected to be cheaper in resource utilization, because the most of the operation ( like detecting and signaling if there are incoming data ) is done in the GCD level. However, it looks to me that Run-Loop scheduling is also good : I'm not sure if Run-Loop scheduling solely depends on polling by the internal loop of run-loop or getting help from unix signal or select() call in the underlying BSD socket library.
Thank you.
JongAm Park
_______________________________________________
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