Marc Blank 2fabab32b9 Don't require sSyncLock for sync error map ... * Use ConcurrentHashMap; check that this provides enough protection for all uses * This resolves known deadlock issues in ExchangeService Bug: 3371039 Change-Id: Ie4ccbe7cdfe8c3d4ec7a0f789409126c8c09f8c4		2011-01-21 18:14:04 -08:00
..
email	Don't modify content URI to non-email providers	2011-01-20 16:28:36 -08:00
exchange	Don't require sSyncLock for sync error map	2011-01-21 18:14:04 -08:00