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

Making the API not require receiver id when connecting #9

Merged
merged 3 commits into from
Sep 15, 2022
Merged

Making the API not require receiver id when connecting #9

merged 3 commits into from
Sep 15, 2022

Conversation

mseltahir
Copy link
Member

Changes:

  • The client now sends the message in JSON format, which contains text message and related metadata fields.
  • Removed receiverID requirement when connecting to the server. The previous logic requires that the client provides the receiverID when connecting to the server, which means the client has to open a new websocket connection every time they want to send a message to a new receiver. This PR makes it so that the client has only one websocket connection, and they can specify the receiver with every message they send in the to field.

@adonese
Copy link
Member

adonese commented Sep 15, 2022 via email

@adonese adonese merged commit 1501c72 into tutipay:main Sep 15, 2022
@mseltahir mseltahir deleted the making-the-api-not-require-receiverID-for-connecting branch September 15, 2022 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants