-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add custom message type support #199
Conversation
Add custom message type support for the following APIs: publish, signal, share file, subscribe and history.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation LGTM - shouldn't we add some test for it?
core/pubnub_coreapi_ex.c
Outdated
result.replicate = true; | ||
result.meta = NULL; | ||
result.method = pubnubSendViaGET; | ||
result.ttl = SIZE_MAX; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In pubnub_publish_defopts method description there is mention of all default values, except ttl and custom_message_type. I think it could be worth to add those as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, we can do it :)
Add `pubnub_set_ipv4_connectivity` and `pubnub_set_ipv6_connectivity` functions to make it possible to enforce specific protocol usage. test(message-type): add subscription test for custom message type Modify subscription integration with additional information about custom message type to check parsing.
Add `pubnub_set_ipv4_connectivity` and `pubnub_set_ipv6_connectivity` to `pubnub_coreapi` to switch preferred connectivity protocol. fix(proxy): add proxy context reset on connection close Make sure that in case of connection close (including because of error) proxy context object will be reset.
Fix issue because of which library with enabled but not configured crypto didn't return message from `pubnub_get_v2`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good to me, compiles well on Windows :)
@pubnub-release-bot release |
🚀 Release successfully completed 🚀 |
feat(message-type): add custom message type support
Add custom message type support for the following APIs: publish, signal, share file, subscribe and history.
feat(ipv6): add connectivity setter
Add
pubnub_set_ipv4_connectivity
andpubnub_set_ipv6_connectivity
topubnub_coreapi
to switch preferred connectivity protocol.fix(proxy): add proxy context reset on connection close
Make sure that in case of connection close (including because of error) proxy context object will be reset.