transitioning to reactor based gRPC server
parent
4367f88c07
commit
ec160cd2d8
@ -1,3 +1,4 @@
|
||||
## Weekly Planning
|
||||
|
||||
[Jan 16-20](weekly/Jan-16-20.md)
|
||||
[Jan 23-27](weekly/Jan-23-27.md)
|
||||
|
@ -0,0 +1,29 @@
|
||||
# Jan 23
|
||||
|
||||
### Connecting Clients to reactors
|
||||
|
||||
**Client -> Server -> Reactor**
|
||||
|
||||
I can take advantage of the private network created via wireguard to allow the server to connected back to individual reactors and then intiate gRPC calls.
|
||||
|
||||
**Pros**
|
||||
- This *VASTLY* simplifies the implementation as I can now connect back to the reactors themselves
|
||||
- from there, I can implement various functions I will need server side
|
||||
- i.e. GetName() SetName() etc.
|
||||
|
||||
**Cons**
|
||||
- I will eventually need to build the wiregaurd implementation
|
||||
- although because its all local network for now, I can plug and play down the road
|
||||
|
||||
### TODO
|
||||
- refactor packages to provide a cleaner interface via simple commands as opposed to the convoluted passing structure that was present with the old I2C library
|
||||
- start working on the interface between the websocket and the reactor
|
||||
- react side this is the actual content that will be rendered by the client
|
||||
- server side this will be a connection to a reactor with the gRPC calls
|
||||
- moving monitoring functionality to the reactor
|
||||
- refactoring to use streaming functionality to avoid needing to re initiate request
|
||||
- have server connect each reactor manager to the rlc
|
||||
- have the reactor manager ping for server info
|
||||
- handle disconnects via exit
|
||||
- sets up cleaner device handling via multiplexing
|
||||
|
Loading…
Reference in New Issue