| | 1 | = Who's working? = |
| | 2 | This exciting project is done by [wiki:gillux] and mentored by [wiki:elb]. |
| | 3 | |
| | 4 | = What's this? = |
| | 5 | == Story == |
| | 6 | Let's start with a little story. You're at home on your desktop and you have Pidgin running. Then you do a little break, and you go to your bed with your laptop, which is also running Pidgin to keep chatting with your friends. Then it's time to go to work, and you go to your office, where you keep chatting discreetly using Finch. |
| | 7 | |
| | 8 | You have 3 clients running, and each have a separate account or handle. Wouldn't it be great if all of these clients were syncronized using the same connections, displayed you the same buddy list and chat logs? Well, that's what detachable sessions allows you to get :) |
| | 9 | |
| | 10 | == The idea == |
| | 11 | The goal of detachable libpurple sessions is to allow a user to have several running libpurple based applications simultaneously, all sharing the same the same data and connections. This involves having libpurple acting as a deamon and clients like Pidgin and Finch connecting to it. All the connected clients will access and display the buddy list, conversations, and chats. Existing ongoing conversations' history will be visible in Pidgin or Finch when they connect to the daemon. |
| | 12 | |
| | 13 | == Goals == |
| | 14 | This project will be managed in two steps. A cool thing would be to allow the clients to be running on ''different machines'' rather than on the same, but this requires to "networkify" all the UI <-> libpurple communication. Such a thing is not simple to do and that's why I will first make it to work with clients on the same machine. This is a minimal goal called ''minimal version'', and having clients on separate machines is an extra goal called ''remote version''. I'll do it if I get the time to. Note that the previous story is still possible with the minimal version if you run the client remotly, using ssh or an export display. |
| | 15 | |
| | 16 | = Details of the hack = |
| | 17 | Here is an outline of how I think to manage this project. |
| | 18 | == Drawing == |
| | 19 | {{{ |
| | 20 | +------------------+ +---------------------------+ |
| | 21 | IM servers<-->[libpurple] Daemon |<--->/ libpurple in \ | |
| | 22 | +------------------+ \detachable mode/ UI Client | |
| | 23 | +---------------------------+ |
| | 24 | }}} |
| | 25 | |
| | 26 | == For the minimal version == |
| | 27 | * '''Deamon wrapper''' Create a deamon program that basically runs libpurple which activates the configured accounts, connect to servers… This daemon also listens for incoming clients connexions. |
| | 28 | * '''Detached mode''' Current standalone mode of clients is kept as a default. Add an option in them to run in detachable mode. The aim is to have to change the libpurple API (and hence the clients) as less as we can. Ideally, they would only have to tell libpurple they want to use the detached mode, and then use it as usual. And all these libpurple calls and events are transparently routed from/to the daemon. |
| | 29 | * '''Attaching and detaching''' Modify the daemon to handle the attaching of a client. It means sending to the client all it needs to be in the current state of the daemon. This includes things like active accounts, buddy list and chat logs. Detaching is much easier but has to be handled aswell. |
| | 30 | * '''Clients syncronisation''' Modify the daemon's libpurple to get a full synchronisation of events coming in and out of all the clients. For example, one client call would appears as an event for the others clients. |
| | 31 | |
| | 32 | == For the remote version == |
| | 33 | 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. |
