F/deserializers

Deserializes data passed to the CakePHP layer via an HTTP request.

Uses a custom DispatchFilter to process the json payload data and deserialize the records (into CakePHP standard data arrays) and set it to the `$this->request->data` property of the Controller.

In essence with this in place your controllers can deal and process with normal data as you would expect.
I can see arguments in both directions.

On the one hand, in our current design, we are actually talking about two very well defined data formats: Cake 2.x style arrays as produced by Model::find() and json-api compatible arrays produced by decoding JSON strings. These are not "generic" serialize or deserialize actions, they are "strongly typed" (to misuse the term) and I can see valid reasoning to make the types being dealt with explicit.

On the other hand, I get the idea of having separate adapters designed to "plug in" different data "types" and wanting to keep the language that this project's code uses generic.

Personally, I think the decision is one of depth. At what point are we no longer asking some adapter to perform it's own version of generic "serialization" and instead asking some method to return a very specific data type or array structure? I'm not familiar enough with the Serializers code layout to offer an opinion on where that line is right now.