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 the opensockets. But the socket seems not to be responding until a reboot. And I'm thinking that I may have a blocking read still in play at that point, and the close socket command doesn't affect it.
-- Mark Wieder ahsoftw...@gmail.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
