-
Notifications
You must be signed in to change notification settings - Fork 3
Use gRPC for middleware TX requests #164
Copy link
Copy link
Open
Labels
back-endAnything that is involved with back-endAnything that is involved with back-endenhancementNew feature or requestNew feature or requestinternal upgradeCode that can be upgraded for better software development experiences and reduced bugsCode that can be upgraded for better software development experiences and reduced bugsmiddlewareIssues relating to middlewareIssues relating to middleware
Metadata
Metadata
Assignees
Labels
back-endAnything that is involved with back-endAnything that is involved with back-endenhancementNew feature or requestNew feature or requestinternal upgradeCode that can be upgraded for better software development experiences and reduced bugsCode that can be upgraded for better software development experiences and reduced bugsmiddlewareIssues relating to middlewareIssues relating to middleware
Define gRPC proto structures and servers to communicate with the server for TX requests. You can define a single
radioTXobject or something with a bytes payload, id number and whatever metadata you want to slap on the end or something. If you have very specific metadata and a bit of it you might need to split up the definition into multiple types. ORRR just drop the ones that are optional and only read them if the packet ID matches. Do some more thinking