On 7/31/2016 10:46 PM, Sannyasin Brahmanathaswami wrote:
AHA.. Yes, "Previous request not complete"
how do we get to these results? "show up in the log " what log?
Sorry, I should have said "my log". My app keeps a text file log of
every server transaction that fails. LibURL errors will be in "the
result" if something goes wrong.
perhaps if you need to reset the API we can issue something like
command resetNetworkInterface
put the openSockets() into tCurrentconnections
repeat for each line x in tCurrentConnections
close socket x
end repeat
end resetNetworkInterface
maybe better practice would be to close the socket after every transfer
operation.
In my case I don't want to terminate the process, since it's important
that every transaction completes. Unless there's a fatal error, the app
must wait until the data is sent. The problem I have been working around
is that the user sometimes continues to execute actions that require a
subsequent transaction and if the first one hasn't completed yet, the
error occurs (usually because their connection is slow or they're moving
very quickly through the app.) I've got something in place that works
most of the time, but not having the problem at all would be a big plus.
I think asyncronous transactions and the much faster tsNet external may
solve that.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
