Craig, put should be blocking, actually, I know it is blocking! I've been blocked by it many times. I don't know why you're experiencing that behaviour at all but I am trying to work around it. I don't know how familiar you are with liburl callbacks. You can basically tell it to execute a command and when that command completes execute something else. In your case you could use liburlftpupload call and pass the callback you want to execute when it complete. Bonus point this is asynchronous so there's no blocking and it doesn't need to have one. You still face the previous request not completed if the thing hangs out forever but I do think it will queue the transactions so that multiple calls just fill a queue but I can recall if that works with ftp calls.
Andre On Mon, Dec 7, 2009 at 4:59 PM, <dunb...@aol.com> wrote: > > In a message dated 12/7/09 1:54:15 PM, an...@andregarzia.com writes: > > Andre. > > I am always trying to change my habits, to use "send in time" instead of > wait. But here I intended it to be used well before the handler actually > does > anything, likely right after the "case" statement. A simple block of errant > keypresses, and no danger, as you pointed out, of anything running amok. > > I get it, though. > > > Craig, > > > > never use a wait call while there's a network transaction going on. > LibURL > > does not like wait commands. > > > > Andre > > > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution