_ _ _ ______ _____ _____ _ _ _ _
| | | | | | | ___ \_ _/ __ \ | | | (_) | |
| | | | ___| |__ ______| |_/ / | | | / \/_____| | | |_ __| | ___ ___
| |/\| |/ _ \ '_ \______| / | | | | |______| | | | |/ _` |/ _ \/ _ \
\ /\ / __/ |_) | | |\ \ | | | \__/\ \ \_/ / | (_| | __/ (_) |
\/ \/ \___|_.__/ \_| \_| \_/ \____/ \___/|_|\__,_|\___|\___/
webRTC
https://google.github.io/styleguide/javaguide.html
thread-safety, deadlock, and race conditions,
volatile keywords
=> The Java volatile keyword is used to mark a Java variable as "being stored in main memory". More precisely that means, that every read of a volatile variable will be read from the computer's main memory, and not from the CPU cache, and that every write to a volatile variable will be written to main memory, and not just to the CPU cache.
local thread
=> The Java ThreadLocal class enables you to create variables that can only be read and written by the same thread. Thus, even if two threads are executing the same code, and the code has a reference to the same ThreadLocal variable, the two threads cannot see each other's ThreadLocal variables.
4 OOP