Feedback Requested

Before we can move on with some major milestones, a few important design questions need to be answered. I wanted to put this out in the open to solicit feedback from users of Camo. The related issues are given for each question, so please submit your feedback there.

Remove Document.create()?

It looks like we can remove this now that Proxies are no longer being used. The question is, do we want to? Since it is already part of the API, it could be useful to keep in case we ever need it in the future. For example, when Proxies were used, the .create() method created a new instance and then applied the Proxy to that instance.

Related issue: #71

Multiple database connections?

Allowing only a single database connection per instance makes Camo easier to work with since you don't need to pass around the database object to all of your models. This is part of why Camo is so easy to use, but it's also limiting to more advanced applications that need to communicate with multiple databases.

Related issue: #73

Modularize database clients?

Should we move the client-specific code to their own modules? This makes sense since it would reduce the module size and reduce unused dependencies. This also makes Camo less user-friendly. Instead of installing with npm install camo, you'd have to do something like npm install nedb camo camo-nedb just to set up your database client. Not hard to do, but also potentially confusing to novices.

Related issue: #62