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

Add API and prefer it over websockets where possible #358

Open
jojomatik opened this issue Mar 27, 2022 · 0 comments
Open

Add API and prefer it over websockets where possible #358

jojomatik opened this issue Mar 27, 2022 · 0 comments
Assignees
Labels
type:feat A new feature
Milestone

Comments

@jojomatik
Copy link
Owner

Is your feature request related to a problem? Please describe.
Currently all information is sent over websocket connections. This works fine but makes truly async implementations of request and response far more complicated. Also I don't think that websockets are not designed to be used this way.

Describe the solution you'd like
Add an API that provides similar information as the current websocket implementations. Use API for initial requests and changes sent from the frontend to the backend. Use websockets for real time updates. Both implementations should use the same types etc. for consistency.

Describe alternatives you've considered
None. The API should be part of 1.0.0 anyways, the implementation in the frontend code should be done at the same time in my opinion.

Additional context
None.

@jojomatik jojomatik added the type:feat A new feature label Mar 27, 2022
@jojomatik jojomatik added this to the v1.0.0 milestone Mar 27, 2022
@jojomatik jojomatik self-assigned this Mar 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feat A new feature
Projects
None yet
Development

No branches or pull requests

1 participant