Mercurial > pidgin.yaz
view doc/imgstore-signals.dox @ 32405:d3d41ba0c3b8
In our forked DNS resolver processes, don't bail out if we get a retryable
error while reading from our parent socket. I think EAGAIN and EWOULDBLOCK
never happen because this is a non-blocking socket AND because we're using
select (seems like we'd be fine using one or the other, and it's not necessary
to use both?). I believe this is correct behavior and we should be doing
this same thing everywhere we read from sockets. I think we probably don't
check for EINTR in many places where we should.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Wed, 24 Aug 2011 17:54:39 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page imgstore-signals Image Store Signals @signals @signal image-deleting @endsignals @see imgstore.h <hr> @signaldef image-deleting @signalproto char *(*image_deleting)(const PurpleStoredImage *img); @endsignalproto @signaldesc Emitted when a #PurpleStoredImage is about to be destroyed. This allows for what amounts to weak references. Code can hold onto a pointer to the PurpleStoredImage without actually "holding" a reference. They can then use a signal handler to let them know when their img is about to be destroyed. @param img The image about to be destroyed. @note It's not possible to purple_imgstore_ref() img to save it. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et