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

createRoom should be idempotent #222

Open
ara4n opened this issue Jan 6, 2017 · 3 comments
Open

createRoom should be idempotent #222

ara4n opened this issue Jan 6, 2017 · 3 comments
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@ara4n
Copy link
Member

ara4n commented Jan 6, 2017

to stop all the clients which don't debounce start chat buttons properly

@turt2live turt2live added the enhancement A suggestion for a relatively simple improvement to the protocol label Jul 19, 2018
@turt2live
Copy link
Member

what kind of approach did you have in mind? The spec so far uses the last parameter to act as a transaction ID - does it make sense to use this same format here?

@KitsuneRal
Copy link
Member

KitsuneRal commented Jul 21, 2018

Doesn't canonical alias serve for a natural mutex for the case? Scratch that, the alias is optional.

@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 6, 2019
@ara4n
Copy link
Member Author

ara4n commented Apr 27, 2020

what kind of approach did you have in mind? The spec so far uses the last parameter to act as a transaction ID - does it make sense to use this same format here?

Yes, to just slap a txn ID on it and use PUT rather than POST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Development

No branches or pull requests

3 participants