Return to Question

edit for readability

Source Link

edit approved Sep 8, 2017 at 13:32

What do we call "ip"IP" and port""port"?

When I'm looping through files and coming up with dynamically created ansibleAnsible playbooks and stuff like that, I've quite frequently havehad to work with a single variable that contains the ipIP and port of something.

Can I refer this as a "socket" or does that name always refer to a handle?

Is it better just to refer to the thing as "$ip_and_port"$ip_and_port or "$address_and_port"$address_and_port or "$host_and_port"$host_and_port?

What do we call "ip and port"?

When I'm looping through files and coming up with dynamically created ansible playbooks and stuff like that, I've quite frequently have to work with a single variable that contains the ip and port of something.

Can I refer this as a "socket" or does that name always refer to a handle?

Is it better just to refer to the thing as "$ip_and_port" or "$address_and_port" or "$host_and_port"?

What do we call "IP" and "port"?

When I'm looping through files and coming up with dynamically created Ansible playbooks and stuff like that, I've quite frequently had to work with a single variable that contains the IP and port of something.

Can I refer this as a "socket" or does that name always refer to a handle?

Is it better just to refer to the thing as $ip_and_port or $address_and_port or $host_and_port?

Source Link

asked Mar 3, 2016 at 22:33

Peter Turner

What do we call "ip and port"?

Can I refer this as a "socket" or does that name always refer to a handle?

Is it better just to refer to the thing as "$ip_and_port" or "$address_and_port" or "$host_and_port"?

naming networking