On 2/22/22 00:52, Mark Waddingham via use-livecode wrote:
Can you clarify what you mean by the 'socket seems to not be responding'?
Sure. Here you go.
I'm communicating between a standalone and a stack in the IDE. I've
tried this with 9.6.3, 9.6.6, and 10.0.0-rc2 with the same results, so I
On 2022-02-21 20:17, Mark Wieder via use-livecode wrote:
On 2/21/22 10:37, Mark Waddingham via use-livecode wrote:
Put another way - if you have done 'close socket i', then it is then
it should be logically impossible for i to be in the openSockets
immediately afterwards.
Ah. Sorry - after i
On 2/21/22 10:37, Mark Waddingham via use-livecode wrote:
Put another way - if you have done 'close socket i', then it is then it
should be logically impossible for i to be in the openSockets
immediately afterwards.
Ah. Sorry - after issuing a closeSocket call the socket does *not*
appear in
t I'm doing now since resetall doesn't do anything
useful. Displaying the opensockets after a resetall still shows the
same sockets as before issuing the command.
And the repeat loop works maybe 50% of the time. It seems that maybe
if I have an active blocking read on a socket it doesn'
On 2/21/22 08:57, Mark Waddingham via use-livecode wrote:
If you want to brute force close all sockets then I suggest:
repeat for each line i in the openSockets
close socket i
end repeat
:)
Yeah, that's what I'm doing now since resetall doesn't do a
On 2022-02-21 16:51, Mark Wieder via use-livecode wrote:
Before I report this one...
I thought resetall was supposed to close open sockets. There's even a
warning in the docs about it being a brute force close. But it doesn't
seem to do anything useful. Am I missing something?
Its
Before I report this one...
I thought resetall was supposed to close open sockets. There's even a
warning in the docs about it being a brute force close. But it doesn't
seem to do anything useful. Am I missing something?
--
Mark Wieder
ahsoftw...
