In prevision of the integration of the 0-robot into the 3bot/digital-me framework it would be nice we add the gedis interface to the robot.
Gedis interface is supposed to be:
faster: it use plain tcp soket
use smaller bandwidth : data is binary encoded
provide automatic generation of client code
To check, It would be nice to have a bi-directional connection between 2 robots. This would be used for even propagation between robot so we can avoid having to constantly pool from the receiving side
Todo:
[x] investigate gedis framework in digital me
[x] convert the REST API object to digital me schema
[x] Implement all API handler as gedis actors
[x] add logic to start the gedis server next to the REST API
[x] Adapt client code so it can choose which interface to use
Code complete and test written. But some recent change in gedis code broke my code. I will park this until gedis is stable again. No point running after something that is still moving that much
In prevision of the integration of the 0-robot into the 3bot/digital-me framework it would be nice we add the gedis interface to the robot.
Gedis interface is supposed to be:
To check, It would be nice to have a bi-directional connection between 2 robots. This would be used for even propagation between robot so we can avoid having to constantly pool from the receiving side
Todo: