I always thought IP6 addresses are too long. Even with 8 bytes, as proposed here, there's 4 billion addresses each for 4 billion people. That should really be enough.
The read threads block because the ReadWriteLock algorithm tries to prevent thread starvation (i.e. when the exclusive lock never gets acquired). Most ReadWriteLock implementation alternate between giving the read locks then the exclusive locks access to the lock.
of course - SRW lock allow shared access only if no waiters ( request to exclusive access) on lock. so even if lock in shared mode, new shared request can block, if was waiter(exclusive) already. in case OP no exactly this, but anyway - i be say that shared access is only hint to system, that it can optimize access - and allow multiple shared threads inside lock. but this was not always
bingo -- the whole system is bankrupt -- they have been papering it over with more and more printing since 2008 but check out curves of M2, national debt, etc. -- isn't going to work, something is going to break
I live in a super high lightning area. No matter how good your protection, if you get struck directly, everything is fried. But that's not your biggest problem as you'll rarely if ever get hit directly. The electronics killer is static electricity that builds up everywhere during an electric storm. For this your DB and plug lightning/surge protectors work quite well. The rod on the roof helps preventing direct strikes, good grounding helps with static build-up. You can even put a copper wire around the perimeter of your property to equalise/move the static electricity. Nothing helps when you get struck directly.
