I wrote a module to resolve similar problems, but in recentely stream2, maybe you can use the new api to read into a buffer larger than 64KB.
https://github.com/freedaxin/head_body_buffers On Saturday, January 26, 2013 6:32:49 PM UTC+8, Bodo Kaiser wrote: > > Hello, > > I am working on a websocket implementation mainly for learn use and am > currently experiencing following issue: > > When I send big data frames (> 65 356 Bytes) I mentioned that this will > cause two data events instead of one. > The WebSocket protocoll does indeed the ability to fragment binary frames > but this approach is actually used by the browser by much bigger frame > sizes. > > In reaction on this problem I now would like to update the highWater marks > on my stream object to match the WebSocket specification is this actually > safe or can this be getting dangerous (memory leaks etc.)? > > Source: https://github.com/bodokaiser/websockets > > Kind Regards, > Bodo Kaiser > -- -- 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, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
