Update of bug #43635 (project gnustep):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #3:
Thanks for that ... I applied the NSStream patch (though not the helper patch
as it conflicted with your TLS helper changes).
I checked on OSX to see if it accepts zero length writes, and it did in a
small test program. So allowing a zero length write is the correct thing to
do from a compatibility point of view.
That being said, I don't think it's a good/elegant thing to do ... it can
result in a process stuck in a busy-wait state as the run loop repeatedly
signals that writing is possible and the handler repeatedly writes nothing. I
actually think having your code set a flag to say writing is possible, and
then clear that flag when it finally writes is generally a better way of
achieving efficient code.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43635>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
