-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{error, incomplete} while decoding nested maps #49
Comments
By default msgpack-erlang use old spec. But msgpack-java uses new spec.
|
Yes, thanks, it helped! |
The point is, that I get messages through net, decode them and save to database aswell, as get from database and sent to net - so it will be very conveniently for me, if I am able to decode these messages from new spec and all strings were binaries, as without {enable_str, true}. Can it be such an opportunity? |
In that case it could be easy to decode binary to construct objects in including strings as binaries, but in encoding, it is hard to tell binary from string. How much could such asymmetric code be tested? |
We're hitting this as well, now that other components are sending us new-spec messages. Using {enable_str,true} fixes the {error,incomplete} issue, but
Please can you suggest a fix that still returns msgpack str as erlang binaries ? As an aside, it's not clear what the intent of "enable_str" is. Lack of documentation doesn't really help. IMHO we should have these options if we want clear compatibility and flexibility:
|
I have this java code to encode package:
As a result - I got binary package:
Then on the Erlang side I am trying to decode it:
Erlang seems to work fine with ordinary map requests, but can't decode nested.
The text was updated successfully, but these errors were encountered: