Skip to content
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

Builder.MessageEncoder This field's type is struct, so I can't override it, it should be message.Encoder #233

Open
hixuzhe opened this issue Aug 9, 2021 · 2 comments
Labels
question Further information is requested v1

Comments

@hixuzhe
Copy link

hixuzhe commented Aug 9, 2021

No description provided.

@henriqueoelze
Copy link
Contributor

Hello @tigerxuz, tks for the issue. Can you provide more details about why you want to override it?
If possible, give us a use case for what you want, so we can analyze if it makes sense or not.

@henriqueoelze henriqueoelze added the question Further information is requested label Aug 10, 2021
@hixuzhe
Copy link
Author

hixuzhe commented Aug 11, 2021

We have a relatively simple custom encoding format, and no handshake mechanism is required.
Pitaya's protocol specification is relatively complex and not suitable for the beginning or middle level client developer.
What we need to use more is the nats related network communication model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested v1
Projects
None yet
Development

No branches or pull requests

3 participants