the transaction will stop if there is a
timeout. (I could be wrong, but libUrl assumes this to be the case and cleans
things up when a socketTimeout message is received) I think the timeout is
measured as the time between any message sent to the remote host and a
subsequent response. So a large download
I need to understand this better. The dictionary says the
socketTimeoutInterval specifies how long to wait before sending back a
timeout message. It sounds like the timeout doesn't affect the data
transmission, it's only a warning, and the data will be sent eventually.
Is that correct?
The
On 10/3/13 2:40 PM, J. Landman Gay wrote:
I need to understand this better. The dictionary says the
socketTimeoutInterval specifies how long to wait before sending back a
timeout message. It sounds like the timeout doesn't affect the data
transmission, it's only a warning, and the data will be
Thanks, that's just what I needed to know.
On 10/3/13 5:11 PM, Phil Davis wrote:
On 10/3/13 2:40 PM, J. Landman Gay wrote:
I need to understand this better. The dictionary says the
socketTimeoutInterval specifies how long to wait before sending back a
timeout message. It sounds like the
On Oct 3, 2013 5:40 PM, J. Landman Gay wrote:
I need to understand this better. The dictionary says the
socketTimeoutInterval specifies how long to wait before sending back a
timeout message. It sounds like the timeout doesn't affect the data
transmission, it's only a warning, and the data will
On 10/3/13 6:01 PM, Roger Eller wrote:
It saddens me to say this, but LiveCode itself has always been iffy at ftp
transfers. I've set the socketTimeoutInterval all over the spectrum, and
never found a solid solution. On the same network, all other FTP clients
would work perfectly every time.
I have a project that will be downloading hundreds of 150MB+ files per
day. Often the file will end with only a few bytes missing, and it doesn't
go back for the rest no matter how long it waits. So, I re-download until
the whole thing is accounted for.
~Roger
On Oct 3, 2013 7:17 PM, J. Landman
, and
libURL keeps trying to send until it goes through. So maybe you don't
need a resend?
Just for the record, the experience I described is with straight TCP
sockets (open socket, read/write, close socket), not HTTP, not FTP. But
I would guess a socketTimeout message probably has the same
