Closed cosparks closed 2 years ago
Going to build out the application with minimal multithreading and see how well it performs (libvlc already runs on its own thread so single-threaded application isn't possible to begin with)
Have some ideas for the main application loop, but still need to work out details on maintaining on-disk and in-memory parity and on networking between the pis
Start to think about how to separate leader vs follower code. Probably just use macros
this issue is too vague to be useful. Closing
Now that you've tested all the hardware and (mostly) gotten everything in working order, it's time to consider how this project will run.
Important considerations: • what states will the program have and how will you transition from one state to another? • how will you deal with intercommunication between threads for these transitions?