You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to use the same approach as for securing the network communication via double-proxy to also support other network protocols.
In this case, the proxy would bridge the gap of the missing network protocol by connecting with the bluechi-agent via unix socket and using the requested network protocol towards the bluechi-controller (or rather the proxy on that side). The agent/controller and the proxy would still use TCP/IP and D-Bus, but the proxies could use any protocol they want. How well each protocol works (performance, fault tolerance, etc.) is a different matter.
How hard would it be to run BlueChi on top of a protocol such as SOME/IP or via UDP?
For the double-proxy approach, probably the forwarding proxy for the respective protocol needs to be implemented (if not available). Then the needed effort depends on the complexity (encryption needed? etc.)
There are environment where the communication between two nodes may not be allowed via TCP.
How flexibile is BlueChi for its network protocols? (especially between the controller and the agent?)
How hard would it be to run BlueChi on top of a protocol such as SOME/IP or via UDP?
The text was updated successfully, but these errors were encountered: