René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve the usage of Sysfs in the interaction with EV3Dev","articleBody":"In the previous Issue:\r\nhttps://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/748\r\n\r\nWe improved the performance with current architecture, the usage of `Sysfs`. `Sysfs` in the current form, is a stateless class with static methods. \r\n\r\nIdeas to improve in this iteration:\r\n\r\n- [ ] Moving from static methods, to instance methods\r\n- [ ] Add `setSysfs` to `Mock` Sysfs to improve testing. Using `Guava`, it could be possible to expose only for testing with the annotation `@VisibleForTesting` but I don´t want to increase the weight of the jar in 2mb.\r\n\r\n@dwalend, what other ideas, do you have?\r\n@JakubVanek, what other ideas, do you have? \r\n\r\nIn your opinion, what state is necessary to maintain in `Sysfs` and have some kind of concurrency protection?\r\n\r\n**Criterias for PR:**\r\n- Branch: `sysfs_perf2`\r\n- Code pass Checkstyle: `gradle checkstyleMain` \r\n- Benchmarks: `JMH`\r\n- Complexity: Reduced\r\n- Number of changes: Minimum\r\n- Tests: Every new class, requiere Unit Tests. Review how to add Concurrency tests to avoid concurrency issues.\r\n\r\nWe will analyse for the classes: \r\n\r\n- [ ] ev3dev.sensors.Battery;\r\n- [ ] ev3dev.actuators.ev3.EV3Led;\r\n- [ ] ev3dev.actuators.lego.motors.EV3LargeRegulatedMotor;\r\n\r\nWe will begin with Battery, an easy case and later, we will tackle a complex case like a Motor.\r\n\r\n![image](https://user-images.githubusercontent.com/147263/103181270-bb0b1e00-489f-11eb-94bb-a43eadb4e15f.png)\r\n\r\nJuan Antonio","author":{"url":"https://github.com/jabrena","@type":"Person","name":"jabrena"},"datePublished":"2020-12-27T22:45:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":83},"url":"https://github.com/765/ev3dev-lang-java/issues/765"}