This seems a very intrusive change at this point, so I have some
questions:
* Does this change the code path/structure for situations where users
use no proxies? I. e. will the "no proxy" case also have a new process
and use the same code path? In other words, what's the regression
potential for the "no proxy" case?
* Why do we need a separate process for this tunneling? It sounds
rather heavy (memory usage, wakeups, startup time, etc.) to have yet
another long-running Python process in the system for protocol
translation, these can usually happen in-process.
* Where does it get the proxy configuration from? Do you use libproxy?
There are quite a few places where proxies are configured
(/etc/environment, GNOME control center, Firefox etc.).
** Changed in: ubuntuone-client (Ubuntu Precise)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929207
Title:
[FFE] Proxy "tunnel" for syncdaemon
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-client/+bug/929207/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
