Try refactoring storage channels / engine without using abstract classes in swarm #2
Milestone
Comments
Burgos
pushed a commit
to Burgos/dmqnode
that referenced
this issue
Sep 6, 2019
Fixes sociomantic-tsunami#2. - Use `VoidBufferAsArrayOf!(cstring)` instead of `cast(cstring[]*)`, which is dangerous because the array length is set after the cast. - Set the array length once instead of appending incrementally. - Use `parseBody` to parse the value to enforce it is the last field in the message payload.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The abstract storage channels / engine classes in swarm are now more of a hindrance than a help. The dmqnode storage system could certainly be refactored in a much cleaner way, without these.
The text was updated successfully, but these errors were encountered: