You where right about using stream.read(0). Giving read the parameter "0" will set the flags so that read(0) will not return any data else it returns data which is getting lost and not anymore available through another read().
Here is now a working gist: https://gist.github.com/bodokaiser/5277842 Am Samstag, 30. März 2013 19:43:35 UTC+1 schrieb kyogron: > > PS: traditional data events are not getting emitted too I just explored > > Am Samstag, 30. März 2013 19:38:28 UTC+1 schrieb kyogron: >> >> Following the docs >> https://groups.google.com/forum/?fromgroups=#!topic/nodejs/hTA91YugVAkit is >> valid to use no parameter on read. read() than should return all >> buffered but I get nothing. >> >> I actually require this for my websocket implementation (which I >> currently switch to streams) but to keep things simple I created a gist >> which shows my problem: >> https://gist.github.com/bodokaiser/5277842 >> >> Am Samstag, 30. März 2013 18:41:10 UTC+1 schrieb Andrew Hart: >>> >>> On Saturday, March 30, 2013 10:23:35 AM UTC-6, kyogron wrote: >>> >>>> this.socket.on('readable', function() { >>>> self.read(); >>>> }); >>>> >>>> >>> What are you doing there? Perhaps you meant read(0)? If not, you might >>> try posting a runnable example. >>> >> -- -- 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.
