Rewrite volunteers about fortune HOT 3 CLOSED

@taylor1791 awesome, there are so many things to be done that I can think of off the top of my head:

• JSON API serializer is a work in progress, it should support all (or most) of the optional MAYs in the spec.
• The database adapter needs to get started on, initially NeDB and MongoDB (since their interfaces are very similar). The adapter should no longer be concerned about the serialization format and just return unformatted objects.
• Pagination is a must, otherwise getting collection indexes will be a nightmare.
• New feature: query method to allow app-specific database queries.
• Look into delegating certain tasks to other libraries, such as routing and JSON Patch. The rewrite will feature a barebones router that can be used with just the built-in http.createServer Node method.
• Public interface should remain largely the same.

I'm working off of the rewrite branch. Anyone is welcome to fork it and send PRs.

from fortune.

@daliwali fwiw, i have a near complete js implementation of a json api server here. i haven't bothered with docs yet, but will do so soon and am happy to answer any questions. it might make sense for fortune to depend on this.

from fortune.

@ethanresnick I took a look at it. what parts can be delegated? looks like there is 100% overlap with what fortune does.

the goal of this rewrite is to decouple everything, from the router to db adapter to serializer, so that the core can be reused whether you are using express/koa/connect or the built-in router, mongodb/nedb/other planned db adapters, or json-api/json-hal/siren or whatever media type. core dependencies will be minimal.

from fortune.