FogBugz (Case [Issue]10102) Network - SocketStream>>next: should not signal ConncetionClosed

A FogBugz case was edited by Sven Van Caekenberghe.

Case ID:      10102
Title:        SocketStream>>next: should not signal ConncetionClosed
Status:       Work Needed
Category:     Bug
Project:      Network
Area:         Misc
Priority:     3 - Must Fix
Milestone:    Later
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/default.asp?10102


Changes:
Status changed from 'Active' to 'Work Needed'.

In Pharo30Inbox

Name: SLICE-Issue-10102-SocketStreamnext-should-not-signal-ConncetionClosed-SvenVanCaekenberghe.1
Author: SvenVanCaekenberghe
Time: 17 April 2013, 9:22:52.011 am
UUID: 69f9efee-eae5-4805-95de-d24d68d5e6bc
Ancestors:
Dependencies: Network-Kernel-SvenVanCaekenberghe.86

Right now, SocketStream>>next: signals ConnectionClosed when less than the requested count of elements are available.

It would be more correct to return a collection of only the elements that could be read, like #next:into: and #next:into:startingAt: do.

This is the underlying cause of a bug where InflateStream>>getFirstBuffer failed, because it used #next: to read 64Kb that sometimes is not available.


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=10102) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker