-
Notifications
You must be signed in to change notification settings - Fork 0
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
Between direct delivery and retrieval from database #15
Comments
Great, should we use UUID or do you have something else in mind? |
Also, do you think the id generation should happen after we receive the message from the ws connection or that we should receive it with the message i.e. the android client generates the message ID? |
I was thinking about uuid |
i don't like them to be generated in the client, but at the same time, i really would love if we have would do as little as possible in the server. the ws in itself is demanding enough |
If we are to use uuid, we should change the message ID type from |
I too would prefer if it was on our side, I don't think it would take more than a few lines and we have the benefit of checking for the rather very unlikely case of key collision. |
ok i will leave this for you |
On it. |
This was resolved in PR #18 |
i think we should generate an id for the message whenever we construct a message. That will allow us to then identify the message and set its
is_delivered
status to true upon sending a messageThe text was updated successfully, but these errors were encountered: