From: Pekka R. <pri...@ik...> - 2006-08-22 06:59:59
|
On Tue, 22 Aug 2006, Mark Doliner wrote: : > Of course the motivation behind this was that if the upper layer is : > for example going to be destroyed before the async call finishes, it : > is now able to abort it before going away, and avoid embarrassing : > crash later when the completion is called back. Gaim might benefit : > of something similar if there are any other async stuff that is : > currently without graceful control. I don't know if similar generic : > solution was already considered but anyways I thought to mention it. : : That's an interesting API, thanks. I kinda feel like right now it would add : more confusion than it's worth, but maybe that's just me. I think I tend to : Yes, you may be right in case of Gaim. In SILC Toolkit where there may be dozens of async library routines that may be used in myriad of different kind of ways and applications, some control for them is necessary... Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |