[concurrency-interest] Pooled executor and data visibility
Philip.Lee at logicacmg.com
Mon May 9 10:31:42 EDT 2005
I am using a PooledExecutor to handle events arriving for a large number
of session objects. If all Runnables passed to the PooledExecutor invoke
Session::work() then can I get away with just making Session::work()
synchronized to ensure that all data modifications are visibile to any
other thread than handles a subsequent event for a that session. Put
another way, do the cache flush/invalidate effects of synchronized
extend to all data fields of all objects touched by calls made within
the synchronized block or are they limited to the object upon which
synchronized is operating. (I'm guessing it's the latter and hoping it's
the former but I haven't seen it spelt out anywhere :).
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
More information about the Concurrency-interest