Richard Miller wrote: >>> We discovered that the pending messages were the source of our file >>> transferring problem. I don't know what the doc's say or when these >>> messages are supposed to be sent, but I do know they greatly >>> effected our file transferring routine, interrupting it at seemingly >>> random times. When we paused them (using a variation on Key Ray's >>> suggestion), the transfer process began working reliably. Perhaps >>> this is a fault in the pending messages system that should be looked >>> into. >> >> Possibly, or the root cause may lie with libURL, or with the way >> libURL is used. >> >> While some libURL calls are blocking, most are asynchronous. If you >> were using any of the non-blocking calls all bets are off with >> regard to pendingMessages, since messages from libURL may easily >> become interleaved with your own. > > Yes.... that was exactly it. We were using a non-blocking transfer, > and pending messages did interfere with it.
There's a blocking form for uploading and downloading available in libURL, and in the last several versions includes callbacks so one can update a progress indicator or do other minor housekeeping. Would that help your situation?
-- Richard Gaskin Fourth World Media Corporation ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com _______________________________________________ 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
