Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Jun 19, 2010, 2:35:15 PM (14 years ago)
- Author:
-
gillux
- Comment:
-
Added the branch name and DBus
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v2
|
|
15 | 15 | |
16 | 16 | = Details of the hack = |
| 17 | Current work may be followed in the '''im.pidgin.soc.2010.detachablepurple''' branch. |
17 | 18 | Here is an outline of how I think to manage this project. |
18 | 19 | == Drawing == |
19 | 20 | {{{ |
20 | | +------------------+ +---------------------------+ |
21 | | IM servers<-->[libpurple] Daemon |<--->/ libpurple in \ | |
22 | | +------------------+ \detachable mode/ UI Client | |
23 | | +---------------------------+ |
| 21 | +------------------+ +---------------------------+ |
| 22 | IM servers<-->[libpurple] Daemon |<--DBus-->/ libpurple in \ | |
| 23 | +------------------+ \detachable mode/ UI Client | |
| 24 | +---------------------------+ |
24 | 25 | }}} |
25 | 26 | |
… |
… |
|
32 | 33 | == For the remote version == |
33 | 34 | Identify then adapt each part of libpurple which aren't remote-friendly, such as audio and video streams or file transfers. For instance in the latter case, files must be transfered to/from the daemon while it sends/receives them. |
| 35 | |
| 36 | == Communication == |
| 37 | DBus will be used to make the daemon<->UI client communication. I needed something that support bidirectionnal calls and over multiple peers. For remote communications there is a TCP layer implemented. However there are some drawbacks in this TCP layer: the lack of authentication and encryption. I plan to overcome those using a custom tunnel as described in [http://fr.dotsec.net/~gillux/detachable_sessions2.svg this drawing]. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!