What kind of 'crash' happens? The mechanism is stable, and I use it a lot.
Several thoughts; 1. Which Treo and what version of OS? I assume Treo 6x0 and OS5, since socket notices were not announced until OS5. 2. I assume you are using the system notification mechanism of socket notices, since I believe that's the only one supported on OS5. I ask, because I do not know if the other socket notice methods are not allowed, or are simply not supported (in other words, weren't ported or don't work). 3. Prior to OS5, the system notification was broadcast deferred, which means you would receive it in the context of whomever performed the next EvtGetEvent(). I do not know how it is implemented in OS5, so I would suggest you not rely on the application context being correct/predictable at the time the system notification is delivered to your handler. For this reason I have always passed a reference to the application context, usually just a copy of the A5 register. I set the A5 register to that of my application, do what I have to do, and then restore the A5 register. This assumes you need access to your application globals. If you do not, choose your own mechanism. Sorry to be so vague. Do you have more detail? -------------------- Jeff Loucks Work 425-284-1128 [EMAIL PROTECTED] Home 253-851-8908 [EMAIL PROTECTED] Mobile 253-691-8812 -----Original Message----- From: a Rachna Tibrewala [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 12:11 PM To: Palm Developer Forum Subject: Socket Notification Hi I m using Socket notification mechanism for receiving data from non blocking socket on a Treo device. I see inconsistent behaviour in the notification callback.It crashes intermittently. Has anyone seen this before.I m not sure of the stability of this mechanism since its not well documented and not widely used by many people. Can anyone help on this. thanks regards rachna -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
