Thanks for the explanations Bjornke. I have been prowling around the web
for more info and found a topic on Stack Overflow attempting to explain the
difference between a socket and a port - lots of responses with many
different analogies! It seems to be a common source of confusion but at
least m
On 15.01.2014, at 01:14, Peter Haworth wrote:
> The dictionary adds to the confusion when, in the write to socket entry, it
> says the socket id is an ip address followed by a port when it's actually
> followed by a socket.
I agree that there's some small inconsistencies in naming sockets vs. po
Thanks John. I think I'm getting a handle on this now. A client connects
to a port and a socket number identifies that client on the port. A server
accepts connections on a specific port but then talks to each client that
connects to it via the socket assigned to the client.
I think the confusi
Hi, Pete. If client A connects to server:10100 from 192.168.0.10:12345,
then the server can send a response back to client A through
192.168.0.10:12345. Each client that connects to the server can be
identified and communicated with in the same way : via the ip:port that
they used to send the
If this doesn´t solve it, can you post your script to show the problem?
If you want a complete example using sockets, you can read the telnet
example on my blog at http://qery.us/43g and if you happen to have my
book, you can also read about sockets there in chapter 18 ;-)
--
Best regards,
Diving into yet another new are of Livecode for me - sockets.
My server issues an accept statement for port 10100. My client opens
socket 10100. WHen the client connects to the server, the port number I
get is not 10100, but some other number which changes on each connection.
When sending messa
