Using serialize/deserialize and #statebox{} about statebox HOT 4 OPEN

Why not just use base64 encoding or fix the python riak client? There are libraries for reading ETF in other languages, including Python.

from statebox.

That said, cross-language interop is not a goal of statebox and you'd have to re-implement it basically in its entirety to correctly use anything serialized with it, since consistency is achieved on read. Given these constraints, ETF is the best serialization as it is fast and compact and requires no transcoding to get the right data structures. Funs are used in the queue, so you will probably have a bad time making this work in JSON.

from statebox.

Thanks for the suggestions. Still, IF I want to do a custom serialization, I can't because the API won't let me, that's my point.

from statebox.

There's nothing truly opaque about records in Erlang. They're just tuples. The API isn't stopping you from doing anything. Sure, it doesn't make it easy for you to do what you think you want to do, but exposing that record definition is going to encourage people to use it, which isn't a good thing. I'd consider adding some kind of to_proplist / from_proplist or something like that, but I'm not sure the use case is really there.

from statebox.