Refactor Reactiveness of Container States

Yukkuricraft / YakumoDash

Webtool for managing all Yukkuricraft software infrastructure

0 stars 0 forks source link

Refactor Reactiveness of Container States #3

Closed remiscarlet closed 4 days ago

remiscarlet commented 2 years ago

We currently have "pseudo-reactiveness" because container states are only updated on HTTP request completion. This means we'll realistically never see a container in a transitioning state.

More generally we don't have a long-living connection between client/server.

Options for implementing:

Streams?
Sockets?
Long polling?
Something else?

remiscarlet commented 1 year ago

e252993373d51ff897c55fd792d8c9d61f37706f starts to address this with the inclusion of SocketIO integration.

remiscarlet commented 4 days ago

Subsumed by #37