mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Alex Tweedly
Sent: Tuesday, November 22, 2016 5:04 PM
To: use-livecode@lists.runrev.com
Subject: Re: Socket communication
Yes, what Richard said :-)
Don't be misled by the dictionary - the socketID *may* start with an IP
address, but it do
'accepted' on.
-- Alex.
On 22/11/2016 21:52, Richard Gaskin wrote:
Ralph DiMola wrote:
> When one enables socket communication on the server side using
> the form "accept [datagram] connections on port portNumber with
> message callbackMessage", how do you stop accepting new connectio
:
Ralph DiMola wrote:
> When one enables socket communication on the server side using
> the form "accept [datagram] connections on port portNumber with
> message callbackMessage", how do you stop accepting new connections?
> The LC lesson show closing all open sockets but no
Ralph DiMola wrote:
> When one enables socket communication on the server side using
> the form "accept [datagram] connections on port portNumber with
> message callbackMessage", how do you stop accepting new connections?
> The LC lesson show closing all open sockets but no
out of use and that would do
it, but I haven't tried it.
Phil Davis
On 11/22/16 1:11 PM, Ralph DiMola wrote:
When one enables socket communication on the server side using the form
"accept [datagram] connections on port portNumber with message
callbackMessage", how do you stop accepting new
That's a really good question Ralph!
Maybe you could put the 'accept' and 'callbackMessage' code in a script
that can be put into use / taken out of use and that would do it, but I
haven't tried it.
Phil Davis
On 11/22/16 1:11 PM, Ralph DiMola wrote:
When one enables socket communication
When one enables socket communication on the server side using the form
"accept [datagram] connections on port portNumber with message
callbackMessage", how do you stop accepting new connections? The LC lesson
show closing all open sockets but not how to prevent new connections.
Than
