Fix datagram issue where available is not correctly updated upon receive.

Fix datagram issue where available is not correctly updated upon receive.

BUG=
R=sgjesse@google.com

Committed: https://code.google.com/p/dart/source/detail?r=40235

[Anders Johnsen, 2014-09-15 08:15:20]

ajohnsen@google.com changed reviewers:
+ sgjesse@google.com

[Søren Gjesse, 2014-09-15 08:20:32]

LGTM!

https://codereview.chromium.org/569173003/diff/20001/runtime/bin/socket_patch...
File runtime/bin/socket_patch.dart (right):

https://codereview.chromium.org/569173003/diff/20001/runtime/bin/socket_patch...
runtime/bin/socket_patch.dart:570: if (result != null) {
Please add a comment that available is only the size of the next datagram, but
that is enough to trigger another READ event.

[Anders Johnsen, 2014-09-15 08:21:37]

https://codereview.chromium.org/569173003/diff/20001/runtime/bin/socket_patch...
File runtime/bin/socket_patch.dart (right):

https://codereview.chromium.org/569173003/diff/20001/runtime/bin/socket_patch...
runtime/bin/socket_patch.dart:570: if (result != null) {
On 2014/09/15 08:20:32, Søren Gjesse wrote:
> Please add a comment that available is only the size of the next datagram, but
> that is enough to trigger another READ event.

Done.

[Anders Johnsen, 2014-09-15 08:21:50]

Committed patchset #3 (id:40001) manually as 40235 (presubmit successful).

[zra, 2014-09-22 16:24:55]

On 2014/09/15 08:21:50, Anders Johnsen wrote:
> Committed patchset #3 (id:40001) manually as 40235 (presubmit successful).

I'm afraid that this will lead to starvation. Is it possible to write a test for
that?

Otherwise, I think we should back out this change, and modify the documentation
to recommend draining the stream using the async method in our email discussion.