Jason, in your turn you've inspired me how to improve candle's usage syntax :) I'll try to implement this later.
Also I've added a benchmark to compare our projects - https://github.com/AlexeyKupershtokh/node-candle/blob/master/benchmark/compare.js My numbers are in the table too. Please check if the benchmark code is fair enough. It measures only the sides that are applicable to the candle. суббота, 10 ноября 2012 г., 22:09:28 UTC+7 пользователь Jason Brumwell написал: > > @Alexey great work on candle, I was looking for something like this for a > project and it had the feature set I needed. The api just didn't feel right > for me, and when I spec'd out how I would write it, it was very close to > cb, so I spent a couple of hours adding the feaures it lacked. > > I wanted to also thank you for creating that table, it outlined a couple > of features that I hadn't thought of but could definitely make use of. > > On Wednesday, October 31, 2012 7:48:56 AM UTC-4, Alexey Kupershtokh wrote: >> >> Here it is: https://github.com/AlexeyKupershtokh/node-candle >> >> it's similar to: >> https://github.com/coolaj86/futures/tree/v2.0/future >> and >> https://github.com/temsa/addTimeout >> to some extent, except that the callbacks are able to free in my case >> allowing to avoid leaks. >> >> As an yet another example, if you use a callback wrapped by >> addTimeout(timeout, cb) or future.once(cb).setTimeout(timeout) as an ACK >> callback for a socket.io request that is never acknowledged, this >> wrapepd callback would exist till the socket is disconnected. >> >> Any response is highly appreciated. >> > -- 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
