Comment 133 for bug 387308
Revision history for this message
| Damiano Albani (damiano-albani) wrote | #133 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I've had a quick look at the internals of the Ubuntu One client.
From what I could figure out, the different components will required specific work to add proxy support.
The SSO component is mainly based on httplib2 and already contains hooks for proxy information.
I managed to hack something out to add proxy support -- that works fine.
As for the sync daemon, it uses the Twisted library which, to my knowledge, doesn't support acting as a proxy client.
I found an old bug report about this issue that dates to 3 years ago. [1]
So maybe the first thing would be to add HTTP/SOCKS proxy support to Twisted if we want to go forward with the Ubuntu One bug.
We could use the Socksipy library to support the various HTTP and SOCKS proxies.
The original Socksipy library has been "forked" by a new "maintainer", so I think it's a good choice.
To those with the knowledge of the Ubuntu One client internals, don't hesitate to correct me.
[1] http://