libpurple in server

[Christopher Baus]

>> Fortunately, this is pretty easy to fix, and completely unrelated to
>> the threaded-ness of libpurple.  We do disk accesses in a *very* small
>> number of well-contained places.
>
> ...and in the case that this does become a problem, that could be
> passed to an I/O thread of some kind, like a write-behind cache.
>

Yes that's my longer term plan.  This is a 1/2 sync 1/2 async architecture
similar to apache 2.5.  It isn't trivial to do right.

http://baus.net/