Skip to content

Is there a way to add custom type by myself? For example, uuid #191

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.

Sign up for GitHub

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

Jump to bottom
Closed
TvoroG opened this issue Jun 2, 2021 · 1 comment
Closed

Is there a way to add custom type by myself? For example, uuid #191

TvoroG opened this issue Jun 2, 2021 · 1 comment
Assignees
@DifferentialOrange
Labels
feature A new functionality

Comments

@TvoroG
Copy link

TvoroG commented Jun 2, 2021

Hey! Thanks for the work!

I cannot figure out the right way to add custom type. msgpack-python supports ext type by ext_hook and default arguments to Packer and Unpacker, but we cannot pass them through tarantool connection. Am I wrong?
@Totktonada
Copy link
Member

Totktonada commented Jun 2, 2021 •
edited
Loading

It seems, you are right. I would make it extensible, more or less in the spirit of PR #154 or PR #190. I'll consider this issue as the feature request.

@Totktonada Totktonada added the feature A new functionality label Jun 2, 2021
@DifferentialOrange DifferentialOrange mentioned this issue Sep 1, 2022
Merged
@DifferentialOrange DifferentialOrange self-assigned this Nov 30, 2022
DifferentialOrange added a commit that referenced this issue Nov 30, 2022
@DifferentialOrange
api: custom packer and unpacker factories
7afb69d 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
@DifferentialOrange DifferentialOrange mentioned this issue Nov 30, 2022
Merged
DifferentialOrange added a commit that referenced this issue Nov 30, 2022
@DifferentialOrange
api: custom packer and unpacker factories
9032f9a 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
DifferentialOrange added a commit that referenced this issue Nov 30, 2022
@DifferentialOrange
api: custom packer and unpacker factories
d158728 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
DifferentialOrange added a commit that referenced this issue Dec 1, 2022
@DifferentialOrange
api: custom packer and unpacker factories
f59e532 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
DifferentialOrange added a commit that referenced this issue Dec 1, 2022
@DifferentialOrange
api: custom packer and unpacker factories
51db95b 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
DifferentialOrange added a commit that referenced this issue Dec 1, 2022
@DifferentialOrange
api: custom packer and unpacker factories
1154b3d 
After this patch, user may pass `packer_factory` and `unpacker_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` supersedes `encoding` option.
`unpacker_factory` supersedes `encoding` and `use_list` options. User
may implement `encoding` and `use_list` support in its custom packer or
unpacker if they wish so. User may refer to request submodule
`packer_factory` and response submodule `unpacker_factory` as an example
(these factories are used by default.)

Closes #145, #190, #191
DifferentialOrange added a commit that referenced this issue Dec 30, 2022
@DifferentialOrange
release: 0.11.0
b3829df 
Overview

  This release introduces the support of crud module API, encoding and
  decoding customization and various security features for Tarantool EE.

Breaking changes

  This release should not break any existing behavior.

New features
  - Support custom packer and unpacker factories (#191).
  - Support [crud module](https://github.com/tarantool/crud) native API
    (#205).
  - Support `ssl_password` and `ssl_password_file` options
    to decrypt private SSL key file (#224).
  - Support specifying authentication method with `auth_type`
    and Tarantool EE `pap-sha256` authentication method (#269).
@DifferentialOrange DifferentialOrange mentioned this issue Dec 30, 2022
Merged
DifferentialOrange added a commit that referenced this issue Dec 30, 2022
@DifferentialOrange
release: 0.11.0
30d5fca 
Overview

  This release introduces the support of crud module API, encoding and
  decoding customization and various security features for Tarantool EE.

Breaking changes

  This release should not break any existing behavior.

New features
  - Support custom packer and unpacker factories (#191).
  - Support [crud module](https://github.com/tarantool/crud) native API
    (#205).
  - Support `ssl_password` and `ssl_password_file` options
    to decrypt private SSL key file (#224).
  - Support specifying authentication method with `auth_type`
    and Tarantool EE `pap-sha256` authentication method (#269).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DifferentialOrange DifferentialOrange

Labels
feature A new functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Totktonada @TvoroG @DifferentialOrange