Re: Fixing socket reads

Here is a second patch, with a third coming some time later. The current stream implementation does not consume its buffered data before starting new reads. That causes serious problems with sockets, of course, if you have an application which exchanges commands/replies with a server. The stream_gets function reads many lines, returns a single one, and then tries to read from the network again. The patch changes the semantic: Consume the buffer first, then call the stream read op. My fgets-based pop3 reader works with this patch already. I suspect that fread exposes similar problems though, but I don't have time right now to improve it similarly. - Sascha