Usage with Active Model Serializers

[bog...@grafidelity.de]

The way AMS separates serialization from business logic is very clean, but at first glance the caching solution of mongoid-cached-json seems to be nice and AMS doesn't have one yet. Is there any feasible possibility to use mongoid-cached-json with AMS?

[Daniel Doubrovkine]

Since the serializer returns JSON I suspect that a solution equivalent to mongoid-cached-json can be built by borrowing the caching parts. But since mongoid-cached-json is effectively the presenter portion as well I doubt that you can mix these two "as-is".

On Thu, Jan 23, 2014 at 9:53 PM, <bog...@grafidelity.de> wrote:

The way AMS separates serialization from business logic is very clean, but at first glance the caching solution of mongoid-cached-json seems to be nice and AMS doesn't have one yet. Is there any feasible possibility to use mongoid-cached-json with AMS?

--
You received this message because you are subscribed to the Google Groups "mongoid-cached-json" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongoid-cached-...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg - artsy.net - github/dblock

[bog...@grafidelity.de]

Thanks for the info. The Active Model Serializers team (Rails core members) is by the way currently evaluating/working on their/one approach to caching. These links are from their public roadmap backlog:

per serializer instance caching
https://github.com/rails-api/active_model_serializers/commit/ee3cec3d0c0d4da6bbf92b428c022a9b1058ba91

Global serializer cache

https://github.com/rails-api/active_model_serializers/pull/89
https://gist.github.com/chancancode/5ad770c4b6c85eebe54c

Maybe your caching part might be compatible to their thoughts.

Am Freitag, 24. Januar 2014 14:17:27 UTC+1 schrieb Daniel Doubrovkine:

Since the serializer returns JSON I suspect that a solution equivalent to mongoid-cached-json can be built by borrowing the caching parts. But since mongoid-cached-json is effectively the presenter portion as well I doubt that you can mix these two "as-is".

On Thu, Jan 23, 2014 at 9:53 PM, <bog...@grafidelity.de> wrote:

The way AMS separates serialization from business logic is very clean, but at first glance the caching solution of mongoid-cached-json seems to be nice and AMS doesn't have one yet. Is there any feasible possibility to use mongoid-cached-json with AMS?

--
You received this message because you are subscribed to the Google Groups "mongoid-cached-json" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mongoid-cached-json+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Daniel Doubrovkine]

So, AMS added caching for JSON output, that's good! What are the features that you're missing (for my personal education)?

Thx

dB.

To unsubscribe from this group and stop receiving emails from it, send an email to mongoid-cached-...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.