[Bug 25304] Should stop hardcoding SOCKS5 proxies and use our own round robin server instead

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 27 12:48:10 CET 2009


http://bugs.freedesktop.org/show_bug.cgi?id=25304





--- Comment #1 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk>  2009-11-27 03:48:09 PST ---
(In reply to comment #0)
> - don't remove proxy from the list once the query has been sent

I'm not sure what's the best algorithm for that. We could do something like:

- first time we need SOCKS5 proxies, send $N requests to proxies from the
fallback list.  If needed reuse the same ones.
- Let's say you received $S1 successful replies from those.
- Next time we need proxies, send 1 (or $N - $S1 ?) queries (here again, reuse
if needed).
- Let's say you received $S2 successful replies from those.
- Drop the oldest proxies to keep the latest $M discovered (with $N == $M?)

This should work pretty well with our round robin server as we'll always get a
pool of working proxies and will continue to refresh it during the lifetime of
the connection.

But that won't work so well for non round robin server. Either they are working
and we'll continue to receive the same host from them. Either they are not and
there is no point to continue to flood them with request. This will lead to
unnecessary traffic to the proxies which is a bit of a shame as we just reduced
it.

Maybe the proxy.telepathy.im should be hardcoded somewhere and handled
differently?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the telepathy-bugs mailing list