api: custom packer and unpacker factories #268
Merged
+224
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After this patch, user may pass
packer_factory
andunpacker_factory
options to a connection. They will be used instead of the default ones.packer_factory
is expected to be a function with the only one parameter: connection object, which returns a new msgpack.Packer object.unpacker_factory
is expected to be a function with the only one parameter: connection object, which returns a new msgpack.Unpacker object.packer_factory
supersedesencoding
option.unpacker_factory
supersedesencoding
anduse_list
options. User may implementencoding
anduse_list
support in its custom packer or unpacker if they wish so. User may refer to request submodulepacker_factory
and response submoduleunpacker_factory
as an example (these factories are used by default.)Closes #154, #190, #191