{"push_id":2936176573,"size":1,"distinct_size":1,"ref":"refs/heads/10-polling_groups","head":"3822a9d3ef6a1840219f53fcd2d9275fd041823c","before":"36d0f77abdac478d4fdb969c470725c8bec11771","commits":[{"sha":"3822a9d3ef6a1840219f53fcd2d9275fd041823c","author":{"name":"Martijn Hemeryck","email":"245ec65841d7639a5605a0c8b0f9d9ae1e8aeaa7@gmail.com"},"message":"Systemic refactor\n\nHuge architectural changes to the codebase to improve reaction time (!)\n\nThe main rationale is now:\n1. read the inputs from the config file\n2. groups them into an arrays of contiguous coils (by address)\n3. assign a modbus client for each of the groups\n4. have each of the groups themselves do their polling -- a\nsemaphore-like construct remains\n5. MQTT: allows handlers to be added per topic at init, so attach them\nthere instead of putting it ine main polling loop.\n\nPlaced everything in a \"re-useable\" modbridge package, with the main\ncode in a \"cmd\" folder.\n\nOther big changes:\n* flags for managing the filename (can now be given as command line\nargument)\n* testing: lots and lots more of it\n* ...","distinct":true,"url":"https://api.github.com/repos/mhemeryck/modbridge/commits/3822a9d3ef6a1840219f53fcd2d9275fd041823c"}]}
{"actor":{"display_login":"mhemeryck"}}