Skip to main content

(iOS) dispatch_async() vs. NSOperationQueue

NSOperation* classes are the higher level api. They hide GCD's lower level api from you so that you can concentrate on getting the task done.
The rule of thumb is: Use the api of the highest level first and then degrade based on what you need to accomplish.
The advantage of this approach is that your code stays most agnostic to the specific implementation the vendor provides. In this example, using NSOperation, you'll be using Apple's implementation of execution queueing (using GCD). Should Apple ever decide to change the details of implementation behind the scenes they can do so without breaking your application's code.
One such example would be Apple deprecating GCD and using a completely different library (which is unlikely because Apple created GCD and everybody seems to love it).
Regarding the matter i recommend consulting the following resources:
Now, regarding your specific questions:
What are the differences between dispatch_*() and NSOperationQueue, [...]
See above.
[...] and is there any reason (technical, performance, stylistic, or otherwise) that I should use one over the other?
If the NSOperation stuff gets your job done, use it.
Is NSOperationQueue just an Objective-C wrapper around dispatch_async, or is there more to it than that?
Yes, it basically is. Plus features like operation dependencies, easy start/stop.


To say, use the highest level api first might sound intriguing. Of course, if you need a quick way to run code on a specific thread, you don't want to write a whole lot of boilerplate code which makes the use of lower level C functions perfectly valid:
dispatch_async(dispatch_get_main_queue(), ^{
But consider this:
[[NSOperationQueue mainQueue] addOperationWithBlock:^{
I'd recommend the latter because most of what you'll write is Objective-C anyway so why not embrace its expressiveness?


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…