cpp: Fixed successive batch updates on same top level key [ATTENTION]
Read access in locked payloads is performed on queued operations before searching the old database. Threads other than the locking thread consistently read the old information. On POSIX, default Lock now also uses boost::thread (instead of pthread) pthread linkage is still present for legacy wrapping. ATTENTION: unlocked payload writing is (by design) not thread-safe (won't crash but data might be inconsistent). Please use Locker armors around all code that might modify a payload in more than one thread. ---> #1: Always use Locker in IU handlers that write to existing IUs!!
Showing
- ipaacalib/cpp/CMakeLists.txt 8 additions, 8 deletionsipaacalib/cpp/CMakeLists.txt
- ipaacalib/cpp/include/ipaaca/ipaaca-locking.h 1 addition, 37 deletionsipaacalib/cpp/include/ipaaca/ipaaca-locking.h
- ipaacalib/cpp/include/ipaaca/ipaaca-payload.h 3 additions, 1 deletionipaacalib/cpp/include/ipaaca/ipaaca-payload.h
- ipaacalib/cpp/include/ipaaca/ipaaca.h 3 additions, 0 deletionsipaacalib/cpp/include/ipaaca/ipaaca.h
- ipaacalib/cpp/src/ipaaca-json.cc 9 additions, 16 deletionsipaacalib/cpp/src/ipaaca-json.cc
- ipaacalib/cpp/src/ipaaca-payload.cc 31 additions, 0 deletionsipaacalib/cpp/src/ipaaca-payload.cc
Loading
Please register or sign in to comment