Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One of the big issues we've been struggling with is getting large ClojureScript data structures with tons and tons of structural sharing (think application state history) 1.) small enough to transmit to the server 2.) for efficient storage.

It sounds like Transit may help with this via its caching etc.? Can someone from Cognitect comment on whether this is a suitable use?



I don't think it can help here - caching only applies to map keys, transit keywords, transit symbols, and transit tags and it's not as of yet configurable.


Ah, bummer. The search goes on then - thanks for the quick reply!


What are you doing instead now? Using event sourcing and replaying events on a server side copy of the client code?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: