Hi Brett, Congrats on the release. I have a few questions though.
1. Could you start adding changelog? Where I work, we're already using couchnode quite a bit and the lack of changelog or release notes doesn't help in my migration path. 2. Why did you remove support for hash keys? We provided the patch for that in the past (after some serious hours of work on that), which got merged, and now I see it gone. Or am I missing something and is it simply "hidden" somewhere? 3. I know you guys use your own gerrit system for git repos, but as you can tell from the 9 open pull requests on GitHub, people want to contribute. If you want to build a community, I reckon it would be a lot more effective if you interacted with your users on GitHub. What are your thoughts on this? On Saturday, August 31, 2013 9:54:58 AM UTC+9, Brett Lawson wrote: > > https://github.com/couchbase/couchnode > > This is a complete rewrite from the 0.0.x releases to significantly > increase speed, stability and consistency. All sample applications have > been rewritten and an API reference has been built to accompany this > release. Additionally, the API itself has been refactored to provide a > much more consistent experience. > > The new API puts a few new arguments in front of the developer, we think > it’s not too obtrusive and makes for a much more uniform interface when > building apps that handle responses. For example, in 0.12.x you would have > done: > > bucket.get( [‘a’, ‘b’], function(err, vals, metas) { > console.log(vals[‘a’], metas[‘a’].cas); > }); > > And now that’s: > > bucket.multiGet( [‘a’, ‘b’], function(err, results) { > console.log(results[‘a’].value, results[‘a’].cas); > }); > > If you’ve used this before, you’ll note that the constructor has changed > slightly as well. Additionally, you can now begin executing operations > against the bucket before it has successfully connected and the operations > will be queued until successful connection or a critical error occurs. > > Before: > couchbase.connect( options, function(err, bucket) { > … handle any errors > bucket.get( … ); > }); > > now is: > > var bucket = new couchbase.Connection(options, function(err) { > … handle any errors > bucket.get( … ); > }); > > or even: > var bucket = new couchbase.Connection(options, function(err) { > > ... handle any errors > }); > bucket.get( … ); > > If you want to see how this comes together in a quick sample and aren’t > offended by browsing beers, check out: > > https://github.com/couchbaselabs/beersample-node > > On performance, this all uses libcouchbase underneath and we’ve made > changes to libcouchbase to work nicely with libuv. Between that and some > other changes, our tests are showing great performance! > > We would like to work quickly toward a 1.0 release. How quickly we get > there depends in part on feedback we receive! We’d love to get your > feedback. > > Brett. > -- -- 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.
