Ignore the kSocketHasBytesAvailable flag in -hasBytesAvailable

If the process goes to sleep just after the kSocketHasBytesAvailable has been raised but before data has been pumped out, when the device wakes up it is possible that the socket is disconnected. Since the flag is up, the application could be hanging waiting for data that does not exist anymore.

For this reason, we are solely relying on what CoreFoundation tells us about data availability. This workaround has proved fixing hangs in the aforementioned case.
Set additional flags on sockets for extra network safety
Merge pull request #1 from robbiehanson/7.4

merge working copy of 7.4
Merge pull request #2 from robbiehanson/master

updating fork
Add explicit error instead of 'nil' when disconnecting socket
Use tab instead of spaces
Pass 'disconnected' error in 'disconnect' socket method
Remove 'strong' modifier from 'delegateQueue'
- fixed compilation error
- added OT podspec
- fixed remote repo in forked podspec
Merge pull request #3 from robbiehanson/master

updating with main repo
deleted vendor and added CocoaLumberjack as submodule
updated submodule
made dynamic framework (iOS 8+/OS X)
- fixed OT version
Preparing for next pod release 7.4.2...
changed submodule branch

was HEAD ???
updated submodule
changed SDK to OS X 10.10
update submodule