[FEAT] Websocket Client API
Closed this issue · 1 comments
NeonDaniel commented
Objective
A more fully-featured client device will need a persistent connection to handle asynchronous events from Neon, i.e. notifications, GUI updates, media playback.
Initial Implementation Requirements
- Ensure Session is properly handled by the MQ connector module or refactor so Hana clients manage their own session
- Update MQ connector module to forward GUI and enclosure events (maybe others)
- Implement an authenticated WS endpoint
Other Considerations
- How should connections to this endpoint be authenticated
- How can events here be documented
- Where should Message context be terminated? (does the client have to care)
NeonDaniel commented
Clients here should maintain session
context locally and supply it with every request