> There is one and only one SEND IN TIME in the app. All the app does is > re-trigger itself to periodically capture data from the internet. Perhaps > there's some weird situation where the trigger happens at the same time as > some external app does its own wait for a response from the internet? I > doubt it, but I've seen stranger things happen in other environments. Maybe > because the internet requests are blocking, Revolution gets "stuck" if it > doesn't get a "proper" response from a GET URL? In that case, the app would > never get control to SEND the message again.
This sounds like the most probably answer, which is why I suggested sending the next message at the start of the handler instead of at the end. Cheers, Sarah _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
