ios - Using GCD or not? -
I have an iPhone app that is a mobile app for a website. Call API methods from our server is the highest everything. The app retrieves user information, and uses the API to update the server.
My colleague and I had a discussion about whether to apply GCD on the aspect of downloading on the app. My colleague argues that since the UI has to wait to complete the download before displaying images, text or anything, there is no need for GCD. My argument is that we have to provide UI rendering (Even so That there is no data), the main thread should be busy, and present the GCD in the app to make other threads for download.
Which logic is right here? In my case, if UI does not provide any data, will there be some kind of interval? Which cleaner, sleek and fast app will give?
If you want one more appropriate question may be to download the asynchronous or main thread for your app. Because there are several different methods for downloading asynchronous on iOS (for example using NTHread, NSOction or actually using GCD), an easy-to-use method may be to use the library. This makes multi-threading networking / internet code very easy to implement and understand.
Personally I am very fond of GCD and you advise to learn it some time soon, although it is not suitable for asynchronous downloading itself as AFNetworking (which is a library That GDI uses under the hood, I believe).
Comments
Post a Comment