Issue status update for
http://smalltalk.gnu.org/project/issue/119
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/119
Project: GNU Smalltalk
Version: <none>
Component: Bindings (other)
Category: feature requests
Priority: normal
Assigned to: bonzinip
Reported by: elmex
Updated by: bonzinip
Status: patch
The Socket>>#flush method in that patch does always use
valueWithoutBuffering.
I would probably introduce a new method with a more verbost name
instead, something like flushWithoutTCPDelay :-)
Yes, an alternative could be a patch that makes #flush not use
TCP_NODELAY, and adds #flushToNetwork which uses it
My reasoning was that when #flush is used, either you *want*
TCP_NODELAY behavior (low latency) or you are not going to write any
data soon to the socket because you're waiting for a reply. In the
latter case, Nagle's algorithm is not going to be useful and the packet
will be sent anyway (only incurring a delay).
In fact, with the kind of high-level buffering that gst performs on
sockets, Nagle's algorithm may even be completely useless...
Do you agree?
_______________________________________________
help-smalltalk mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
