But basically. Currently the walkietalkie is only able to send from the host and then, if request, expect a reply from the esp32.
This is a tadbit naive imo.
What we should do is have a system for expected replies and for unsolicited messages.
We need to ID them somehow and have an asynchronous listener waiting for the messages and tag them somehow and then a callback. Will think of that later, but it is needed.
Should also rename it? Get rid of the silly name
But basically. Currently the walkietalkie is only able to send from the host and then, if request, expect a reply from the esp32.
This is a tadbit naive imo.
What we should do is have a system for expected replies and for unsolicited messages.
We need to ID them somehow and have an asynchronous listener waiting for the messages and tag them somehow and then a callback. Will think of that later, but it is needed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Should also rename it? Get rid of the silly name
But basically. Currently the walkietalkie is only able to send from the host and then, if request, expect a reply from the esp32.
This is a tadbit naive imo.
What we should do is have a system for expected replies and for unsolicited messages.
We need to ID them somehow and have an asynchronous listener waiting for the messages and tag them somehow and then a callback. Will think of that later, but it is needed.