It is thread safe in the sense it will still generate random numbers when used by multiple threads. The Sun/Oracle JVM implementation uses synchronized and AtomicLong as seed to improve consistency across threads. But it doesn’t appear to be guarenteed across all platforms in the documentation. I wouldn’t write your program to require such a … Read more
How about Thread.sleep(2000); ? 🙂
Python’s built-in structures are thread-safe for single operations, but it can sometimes be hard to see where a statement really becomes multiple operations. Your code should be safe. Keep in mind: a lock here will add almost no overhead, and will give you peace of mind. https://web.archive.org/web/20201108091210/http://effbot.org/pyfaq/what-kinds-of-global-value-mutation-are-thread-safe.htm has more details.
In the absence of synchronization this code Object a; public boolean test() { return a != a; } may produce true. This is the bytecode for test() ALOAD 0 GETFIELD test/Test1.a : Ljava/lang/Object; ALOAD 0 GETFIELD test/Test1.a : Ljava/lang/Object; IF_ACMPEQ L1 … as we can see it loads field a to local vars twice, it’s … Read more
This method is 100% thread safe, it would be even if it wasn’t static. The problem with thread-safety arises when you need to share data between threads – you must take care of atomicity, visibility, etc. This method only operates on parameters, which reside on stack and references to immutable objects on heap. Stack is … Read more
-pthread tells the compiler to link in the pthread library as well as configure the compilation for threads. For example, the following shows the macros that get defined when the -pthread option gets used on the GCC package installed on my Ubuntu machine: $ gcc -pthread -E -dM test.c > dm.pthread.txt $ gcc -E -dM … Read more
Eric Lippert has a nice blog post entitled What is this thing you call “thread safe”? about the definition of thread safety as found of Wikipedia. 3 important things extracted from the links : “A piece of code is thread-safe if it functions correctly during simultaneous execution by multiple threads.” “In particular, it must satisfy … Read more
You can’t use global variables to hold this sort of data. Not only is it not thread safe, it’s not process safe, and WSGI servers in production spawn multiple processes. Not only would your counts be wrong if you were using threads to handle requests, they would also vary depending on which process handled the … Read more
It seems just fine to me. There is nothing in the GSON instance that makes it related to a specific instance of LoginSession, so it should be static. GSON instances should be thread-safe, and there was a bug regarding that which was fixed.
If you are targetting .Net 4 there are a few options in System.Collections.Concurrent Namespace You could use ConcurrentBag<T> in this case instead of List<T>