On 9/13/06, James M Snell <[EMAIL PROTECTED]> wrote:
Currently the FOM Interface are not threadsafe. For instance, if multiple threads try to call entry.setId(...) at the same time, it could cause some rather interesting results. However, synchronizing the methods by default causes a very significant performance drop. I propose that we simply take it as a given that the FOM objects are not threadsafe and that end developers, if they want to allow multiple threads to modify individual FOM objects, they must provide the necessary synchronization.
+1, synchronizing those objects seems like a horribly wasteful idea, considering how seldom they are likely to be used from multiple threads. -garrett
