Difference between revisions of "Swift Tips and Best Practice"
From Hawk Wiki
(→Gran Central Dispatch) |
m (→Do not pass objects between threads) |
||
| Line 17: | Line 17: | ||
* Abstract thread pool pattern | * Abstract thread pool pattern | ||
* Better performance | * Better performance | ||
| − | ===Do not pass objects between threads=== | + | ====Do not pass objects between threads==== |
Instead, use an observer. Send notification when the object is updated in the sub-thread, then in the main thread, subscribe to the notification, fetch data when got notification. | Instead, use an observer. Send notification when the object is updated in the sub-thread, then in the main thread, subscribe to the notification, fetch data when got notification. | ||
Latest revision as of 03:45, 17 March 2015
Contents
Multi threading pro tips
NSData(contentWithUrl: url)
Do not use this for network request. Because it is synchronized and it may block your UI a tens of seconds.
Run Loop
It's the main thread run()
- Handle UI Input
- View Drawing
- Animation
- More
You have 17ms to do stuff in the main thread.
Threading
If you want to some intensive computation. Use another thread.
NSThread
old method Clumsy and poor. Do not use.
Grand Central Dispatch
- Abstract thread pool pattern
- Better performance
Do not pass objects between threads
Instead, use an observer. Send notification when the object is updated in the sub-thread, then in the main thread, subscribe to the notification, fetch data when got notification.
