Changes between Version 16 and Version 17 of WhatIsLibpurple

Timestamp:

Aug 9, 2009, 10:56:54 PM (14 years ago)

Author:

Robby

Comment:

adium.im

WhatIsLibpurple

@@ -4 +4 @@
 
 = Who uses libpurple? =
- * [http://www.adiumx.com/ Adium] - A user-friendly graphical IM program for OS X.
+ * [http://www.adium.im/ Adium] - A user-friendly graphical IM program for OS X.
  * [http://www.apolloapp.com/ Apollo IM] - IM application for the iPhone and iPod Touch.
  * [http://www.eqo.com/ EQO] - An IM program for mobile phones.
@@ -28 +28 @@
 = Is it threaded? =
 
-libpurple is ''not'' threadsafe.  It should be accessed by an implementing UI only one thread ''ever'' (that is, do not attempt to use synchronization or locks to access it from multiple threads).   Plugins can use multiple threads, but they must always call libpurple functions and callbacks on the thread on which they were initialized (typically the main thread of the program).
+libpurple is ''not'' threadsafe. It should be accessed by an implementing UI only one thread ''ever'' (that is, do not attempt to use synchronization or locks to access it from multiple threads). Plugins can use multiple threads, but they must always call libpurple functions and callbacks on the thread on which they were initialized (typically the main thread of the program).
 
-libpurple's run loop access occurs through eventloop.c; the UI must implement the UI Ops defined there and register them in order to watch sockets for new data and call timeout functions after a specified delay.  For example, Pidgin uses the glib run loop, and Adium uses the Cocoa event run loop.
+libpurple's run loop access occurs through eventloop.c; the UI must implement the UI Ops defined there and register them in order to watch sockets for new data and call timeout functions after a specified delay. For example, Pidgin uses the glib run loop, and Adium uses the Cocoa event run loop.