[Pidgin] WhatIsLibpurple modified

[Pidgin]

Changed page "WhatIsLibpurple" by no_se from 89.0.154.118*
Page URL: <http://developer.pidgin.im/wiki/WhatIsLibpurple>
Diff URL: <http://developer.pidgin.im/wiki/WhatIsLibpurple?action=diff&version=23>
Revision 23
Comment: removed spam

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: WhatIsLibpurple
=========================================================================
--- WhatIsLibpurple (version: 22)
+++ WhatIsLibpurple (version: 23)
@@ -23,13 +23,13 @@
 
 = Can you give me some details? =
 
-Your application will first initialize the core (purple_core_init),[http://www.vilamalsvetikliment.com/ Ohrid] add plugin-search paths, load the saved plugins, prefs etc.  Your best bet is to check out a copy of the source code and look at finch/finch.c:init_libpurple().
+Your application will first initialize the core (purple_core_init), add plugin-search paths, load the saved plugins, prefs etc.  Your best bet is to check out a copy of the source code and look at finch/finch.c:init_libpurple().
 
 = 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 [http://pinkeyesymptomstreat.com pink eye symptoms], 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 [http://www.findermind.com/tag/best-background-check-services-companies/ best background check service] 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.
 
 = Where to get it? =
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
Pidgin <http://pidgin.im>
Pidgin

This is an automated message. Someone at http://pidgin.im added your email
address to be notified of changes on WhatIsLibpurple. If it was not you, please
report to .