The series is great and I’m really happy I found it because it’s a marvelous refresher on GCD up to now ! I think though the network manager should not used combine as an example, also in the dispatch group video by the way. Firstly it leads to a misunderstanding of its observe(on)/ receive(on) method and secondly it hides the strength of building a pipeline to produce the same result.
Great video. I would suggest though that if someone really wants to do something like search with Combine that they use ".debounce" instead of a workitem. Understand this was just a contrived example, but I could see someone using this when debounce is much more streamlined for this purpose.
In one of the interview of iOS, I got this question if out of two API, one's output is not that much important and it should proceed though that one API fails to return, I wish I could have seen this video before. But no worry, it's never late to start again. Thanks for this informative session with detailed analysis on each edge cases. Thanks
Hi @Pallav. Thanks for this great video. i've one query. You've used DispatchTimeoutResult for getting the success or timeout and accordingly navigate to next screen. So, here, as 3 seconds is set, so timeout occurs and the API is call is not completed and navigated to next screen. But, can you please tell what should be the approach if we want the API to be completed after the navigation happens to the next screen?
@pallav for the checkUsernameAvailability case, you are assuming that the API response would take approximately the same amount for each string. Otherwise, there could be a scenario wherein the user types 2 letters(say "Pa") and then stops for say 1.1 seconds. At this point, the API has started but the response is not achieved for say next 4 seconds. Now the user starts typing again. Now the API is fired for "Patrick" after a 1-second delay. Now the response of "Patrick" comes before the response for "Pa". This would lead to the wrong error being shown or not when both the username availability is different. Say if "Pa" is not available but "Patrick" is available. We would end up seeing an error on "Patrick". BTW Great content.
Hi Pallav, Just awesome, I would like know from your source code How can we write Unit Testing for NetworkManager? If you can provide some guidelines it will be great. Thank you bhai.
Feedback. I don’t care how long these videos are. I just need to learn all of this. 👍🏼
Glad you like them!
Please cover modern swift concurrency in this series too. Thanks!
Thanks! Pallav this tutorial is one of the best with simple and clean teaching.
The series is great and I’m really happy I found it because it’s a marvelous refresher on GCD up to now !
I think though the network manager should not used combine as an example, also in the dispatch group video by the way. Firstly it leads to a misunderstanding of its observe(on)/ receive(on) method and secondly it hides the strength of building a pipeline to produce the same result.
I have watched upto 3rd part of mastering in concurrency series. Excellent!!!
Thanks, Pallav for coming up with such topics. it's really informative and useful for the Dev community.
videos are not long..these are elaborate...covering minute details..thanks a lot!
Great video. I would suggest though that if someone really wants to do something like search with Combine that they use ".debounce" instead of a workitem. Understand this was just a contrived example, but I could see someone using this when debounce is much more streamlined for this purpose.
In one of the interview of iOS, I got this question if out of two API, one's output is not that much important and it should proceed though that one API fails to return, I wish I could have seen this video before. But no worry, it's never late to start again. Thanks for this informative session with detailed analysis on each edge cases. Thanks
Thanks Pallav, I have been looking for this kind of explanation and content.
thanks @Pallav for informative session.Waiting for next more sessions. Good idea to cover one topics in one small session
Oh yes! Thanks for posting the next!
thanks for making these series. I benefited alot. thank you!
Thank you sir for great explanation
Hi @Pallav. Thanks for this great video. i've one query. You've used DispatchTimeoutResult for getting the success or timeout and accordingly navigate to next screen.
So, here, as 3 seconds is set, so timeout occurs and the API is call is not completed and navigated to next screen. But, can you please tell what should be the approach if we want the API to be completed after the navigation happens to the next screen?
Kindly start creating the videos of the new terms swiftUI as well.
Great explanation, keep going
@pallav for the checkUsernameAvailability case, you are assuming that the API response would take approximately the same amount for each string. Otherwise, there could be a scenario wherein the user types 2 letters(say "Pa") and then stops for say 1.1 seconds. At this point, the API has started but the response is not achieved for say next 4 seconds. Now the user starts typing again. Now the API is fired for "Patrick" after a 1-second delay. Now the response of "Patrick" comes before the response for "Pa". This would lead to the wrong error being shown or not when both the username availability is different. Say if "Pa" is not available but "Patrick" is available. We would end up seeing an error on "Patrick".
BTW Great content.
Great thought !
I think this case should be handled from server side. I don't know about the technique but may be something similar to our.
Great explanation !!!
Hi Pallav, Just awesome, I would like know from your source code How can we write Unit Testing for NetworkManager? If you can provide some guidelines it will be great. Thank you bhai.
hi @pallav. Can you make a tutorial on how to make network Calls?
Nice, keep posting
Hi @pallav. This is really great. Can you also post videos on operation queues as well ?It will be really beneficial
still didn't understood why the global workitem is initaialised with local yet the execution is done on workitem asyncafter
please discuss how to resolve data inconsistency in concurrency
I’ve discussed that in next video (coming this Saturday)