Javadoc clarification
Revert "Use our LTQ" - performance is not what we hoped

This reverts commit 62a8d935d25af7a72cfe5d67767aa7faf75b3b48.
Prep 3.1.0.Beta7
Next is 3.1.0.Beta8
Provide old-locking mode for broken JDKs that synch on everything NIO-related
[XNIO-185] Only compact throughBuffer if not all data was transfered
Fix CAS on exitWrite of FixedLengthStreamSinkChannel
Remove volatile writes from hot path when read or write timeouts are not configured for a channel
Do not require volatile writes to update channel listeners
[XNIO-186] Relax thread-safety of FixedLengthStreamSinkChannel
[XNIO-186] Relax thread-safety of FixedLengthStreamSourceChannel
[XNIO-186] Relax thread-safety of PushBackStreamChannel (also fix misc small bugs and performance issues)
Seed last read/write values when the timeout is set
Remove volatile writes from hot path when read or write timeouts are not configured for a half-duplex channel
Unused class, RIP LTQ
Prep 3.1.0.Beta8