View Single Post
Old 09-02-2009, 11:26 AM   #35
=X=
Wizard
=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.
 
=X='s Avatar
 
Posts: 3,671
Karma: 12205348
Join Date: Mar 2008
Device: Galaxy S, Nook w/CM7
Quote:
Originally Posted by kovidgoyal View Post
It's a little hairy in this case, as you would have to deal with concurrent processes modifying the database.
It does add more complexity but not by much. Adding a simple semaphore to block any writes and allow reads is not very complicated. Minimal compared to the boost in user experience.

Reading/Writting to databases only gets complicated when you have a host of clients that read/write to the same database.

=X=
=X= is offline   Reply With Quote