Aaron Heckmann

sounds good to me

that's actually how it works today. we just wrap the passed collection in a compatibility layer. We should break the layer out and define it so its easy to create...

so you need access to the fields/options etc? we could expose that.

Right now if you override mquery.Collection we'll use that instead but it must conform to the mquery collection API. take a look at lib/collection

that sounds good for now. maybe nice to provide a clean env abstraction which provides the collection,objectid,readpref etc.

A goal of this module is to fail as fast as possible on invalid input. No guessing means less bugs in my APIs. Accepting multiple formats by using an array...

nope didn't miss it. still need to add the TTL index and an extra date field. just haven't gotten to it yet.

yes. manually we'll run into a lot of the same considerations but also have to write the code ourselves. we'd also need to somehow account for more than one app...

yeah definitely eat to split this up more. this is a first pass. want me to add you?

s/eat/want haha