Mar. 7th, 2012

Threads

Mar. 7th, 2012 02:49 pm
philkmills: Phil and guitar (Default)
When I started this, I was handling background database updates by keeping control of which thread was allowed access at any one time. This worked fine for simple cases but was starting to look top-heavy. The recommended method is to have each thread maintain its own "scratchpad" of modified objects and, when there's a commit, merge the changes into any other affected threads.

It took a bit of a rewrite compared to the simple template code for Core Data that Apple provides but it looks as if it will be easy to work with from here on.

Bug score: Open 13, Fixed: 75.

April 2012

S M T W T F S
1234567
891011121314
15161718192021
2223 2425262728
2930     

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 25th, 2017 12:46 am
Powered by Dreamwidth Studios