{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Jason Townsend <[EMAIL PROTECTED]>
on 2/17/02 11:58 PM, Jason Townsend <[EMAIL PROTECTED]> wrote:
> on 2/17/02 6:58 PM, Jason Townsend <[EMAIL PROTECTED]> wrote:
>> Looks like the notification which would cause a reconnect/update of the UI
>> is not getting sent in the SIGPIPE case. Here's a guess at what the fix
>
> OK, this isn't the right fix. With my change in the next time I got the
> SIGPIPE Fire crashed instead of just disconnecting Yahoo. The real fix is
> probably to post an event or something since certain operations are not safe
> inside a signal handler.
I checked in my second cut at this... I schedule an NSTimer in the signal
handler which calls the function to indicate that Yahoo is disconnected the
next time the main thread gets an event. This hasn't crashed for me, and it
successfully reconnected after the SIGPIPE.
-Jason
--
<http://homepage.mac.com/townsend/>
"If you don't know where you want to go, we'll make sure you get taken."
- Microsoft ad slogan, translated into Japanese.
{#} ----------------------------------------------------+[ fire ]+---
