Skip to content

feat: websocketWidget advice and guidance #252

@aktxyz

Description

@aktxyz

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions