> You're still doing it wrong. This is like complaining that you can't tell a
> stream is ended because you waited to attach an `end` event handler.
But that's supported, now :) If you don't consume the stream, it
never emits 'end', even if it never has any data. You still have to
read() or on('data') or resume() it.
You could argue that the 'readable' is only for state transitions, I
suppose, and the correct approach is to try to read, and only wait for
'readable' if there's nothing there. But there's little harm in
re-emitting the event, at least the first time, and it's an easy
change to make. (We already special-case 'data' and 'readable' for
other reasons.)
Part of the reason why this is an issue for you is that the HTTP
implementation's interaction with the TCP layer is utter shit. Look
for changes there in 0.12. In the meantime, we should make this work,
if only because some other crappily-built stream is likely to be
similarly broken in this surprising way ;)
Taking the bug report to an issue is 100% the correct move, thanks.
Let's continue the discussion of that specific point there.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
