Working with objects, serialization & defaults

[willviles]

Working with objects, serialization & defaults

[marcoow]

I'd be interested to hear more as to why you say storing objects in cookies isn't advisable

You might run into problems with max cookie size, having to migrate data in cookies etc. In general you want to store only enough information in a cookie to be able to restore your full state from that. For more advanced things it's probably better to use localStorage or sessionStorage or even things like IndexedDB or so.

and whether you think it'd be worth me authoring an accompanying plugin - something like Ember Cookies Object Store?

I think everything's worth exploring ;)

[marcoow]

Thanks for the great writeup!

I honestly don't believe this is something that belongs in ember-cookies though. The idea behind ember-cookies is really to provide a low level cookies API that works both in the browser as well as in Node. Introducing functionality that allows using cookies as an object store that also has to deal with serialization etc. introduces a lot of additional complexity that just isn't necessary for the majority of use cases. Also using cookies in this way isn't actually advisable I'd argue (there might be edge cases in which doing this is actually fine and your app might be one of these edge cases) and I don't think we should advocate this kind of usage by providing dedicated APIs for it.

[willviles]

@marcoow I totally understand that and in fact I thought that would be the case!

I'd be interested to hear more as to why you say storing objects in cookies isn't advisable and whether you think it'd be worth me authoring an accompanying plugin - something like Ember Cookies Object Store?