> On Feb 13, 2017, at 3:02 PM, Quinn The Eskimo! <eski...@apple.com> wrote: > > That’s the correct approach. Repeatedly calling `-read:maxLength:` inside > your `.hasBytesAvailable` handler can cause various odd problems, not least > of which is the starvation of other streams scheduled on the same run loop.
Then I’m back to the question of why this problem is occurring. Somehow I am not being notified of data available on the stream. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com