Skip to content

feat: websocketWidget advice and guidance #252

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

Open
aktxyz opened this issue May 16, 2025 · 0 comments
Open

feat: websocketWidget advice and guidance #252

aktxyz opened this issue May 16, 2025 · 0 comments
Labels
feature New feature or request

Comments

@aktxyz
Copy link
Contributor

aktxyz commented May 16, 2025

I am working on a websocket widget wsWidget and need some advice/guidance

The 2 key things I want on the first pass are

  1. establish a nailed up websocket based on the provided url in the wsWidget json fragment, the websocket would be in a pool managed by stac and not get recreated over and over, you could have multiple websockets as long as they have different urls

  2. ADVICE here is were I could really use some guidance ... one of the 'commands' that can come down over the websocket would be networkWidgetReload:name ... and this should somehow trigger the identified networkWidget to reload.

I don't think there is any listener/observer/setstate type thing floating around in stac yet ... any advice here on a good way to go about this?

@aktxyz aktxyz added the feature New feature or request label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant