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

Websockets from Frontend to Backend (Internal comm) instead of being initiated from the client's browser #483

Open
amour86 opened this issue Nov 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@amour86
Copy link

amour86 commented Nov 24, 2024

Is your feature request related to a problem? Please describe.
No, but better reusability and architecture

Describe the solution you'd like
Websockets to backend container should be initiated from frontend to backend instead of being initiated from the browser. by this architecture it will be complying with the 3-tier standard and it will minimize the WS connection errors.

Describe alternatives you've considered
Websockets to backend container should be initiated from frontend to backend instead of being initiated from the browser

Additional context
Add any other context or screenshots about the feature request here.

@amour86 amour86 added the enhancement New feature or request label Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant