Changes between Version 28 and Version 29 of WhatIsLibpurple


Ignore:
Timestamp:
01/09/14 16:20:49 (5 years ago)
Author:
MarkDoliner
Comment:

Attempt to improve wording.

Legend:

Unmodified
Added
Removed
Modified
  • WhatIsLibpurple

    v28 v29  
    2727= Is it threaded? =
    2828
    29 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).
     29libpurple is ''not'' threadsafe. It should only be accessed by 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).
    3030
    3131libpurple'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.
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!