You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when sending search results from Tribler to the Java GUI, all found results are send every time new results are found. Because of this, the already found results have to be filtered out. This causes significant overhead in the sending and filtering of the results. An easy solution would be to send only new results.
The text was updated successfully, but these errors were encountered:
Should this still be done? (eg create a torrents.get_remote_results(int) that ignores the oldest int results, instead of polling torrents.get_remote_results_count())
Currently, when sending search results from Tribler to the Java GUI, all found results are send every time new results are found. Because of this, the already found results have to be filtered out. This causes significant overhead in the sending and filtering of the results. An easy solution would be to send only new results.
The text was updated successfully, but these errors were encountered: