9b458c63e0
I've removed any mention or dependency of TorrentManager from Manager. There is still more work to do, but Messenger now communicates directly with a TorrentManager rather than asking the communities Manager to handle it. I've ensured that LogStdout() is only called from TorrentManager and removed entirely from Manager, this functionality seems to be some kind of debug tool specifically for torrent related functionality. Next I need to focus on functions within Messenger that call a TorrentManager and see how to isolate these from the main flows, following that I also need fix the tests that are broken. I will also need to refactor torrentClientReady() so that it is a function of TorrentManager, this may allow for pushing more functions into TorrentManager which will lead to better torrent encapsulation. |
||
|---|---|---|
| .. | ||
| accounts | ||
| appmetrics | ||
| browsers | ||
| chat | ||
| communitytokens | ||
| ens | ||
| ext | ||
| gif | ||
| local-notifications | ||
| mailservers | ||
| peer | ||
| permissions | ||
| personal | ||
| rpcfilters | ||
| rpcstats | ||
| shhext | ||
| status | ||
| stickers | ||
| subscriptions | ||
| typeddata | ||
| updates | ||
| utils | ||
| wakuext | ||
| wakuv2ext | ||
| wallet | ||
| web3provider | ||