[Pidgin] #73: Concurrent libpurple UIs might break stuff

[Pidgin]

#73: Concurrent libpurple UIs might break stuff
------------------------+---------------------------------------------------
  Reporter:  bleeter    |       Owner:  nwalp
      Type:  defect     |      Status:  new  
  Priority:  major      |   Milestone:       
 Component:  libpurple  |     Version:  2.0  
Resolution:             |    Keywords:       
   Pending:  0          |  
------------------------+---------------------------------------------------
Comment (by sadrul):

 I think it'd be interesting to use our dbus-interface, if possible, to
 manage situations like this. Something like the following:

  * When purple tries to load data (accounts/prefs etc.), it first tries to
 connect to an already-running purple client. If it succeeds, then instead
 of loading data from the files, it gets the data over dbus.

  * When writing, it again tries to communicate over dbus first. If that
 fails, it writes on the files.

 I think Guifications-3 will provide functionalities like this, but Gary
 will know better.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/73#comment:2>
Pidgin <http://pidgin.im>
Pidgin