AadamZ5 / AadamZ5/dev-disp

Implement PoC stream to test webpage via websocket

Aperta
#3 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Rust
Stelle
3
Fork
1
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

To get this off the ground, we should implement a basic client as a web-app. This will allow us to build out the transport layer without worrying about complexity of a real client app.

- We may need to solve how to encapsulate generic messages from the core system in any transport. How can they become serializable in any means? Chat with copilot.
- For example, core business logic has defined messages. Each transport may need more metadata or other messages in addition to the core messages. Should each transport define it's own duplicate set of messages? Or can they somehow wrap the existing core business logic messages? We also can't assume how each transport wants to serialize and de-serialize messages (if at all), meaning the core messages need to be serializable in any capacity. Is just implementing `serde` enough for that?
- *Probably yes for now*

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

The issue is about designing a transport layer for serializing core business logic messages. Start by examining the existing core message definitions and the serde crate usage. Look for any existing websocket or transport code. The goal is a PoC web-app client, so research how to set up a basic Rust websocket server and a simple web frontend to connect to it.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
backend, web-dev
Tipo di issue
Funzionalità
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.