Talk:Parse an IP Address: Difference between revisions
Content added Content deleted
(→Port 0) |
(→Port 0: IP, not TCP or UDP.) |
||
| Line 38: | Line 38: | ||
: TCP and UDP never use port 0. Sockets use port 0 to mean "port not specified". The meaning of "port not specified" changes with context. With a server socket, during a bind() to "port not specified", system chooses a default port in range 49152 to 65535. With a server socket, port 0 is same as "port not specified". --[[User:Kernigh|Kernigh]] 22:13, 28 September 2011 (UTC) |
: TCP and UDP never use port 0. Sockets use port 0 to mean "port not specified". The meaning of "port not specified" changes with context. With a server socket, during a bind() to "port not specified", system chooses a default port in range 49152 to 65535. With a server socket, port 0 is same as "port not specified". --[[User:Kernigh|Kernigh]] 22:13, 28 September 2011 (UTC) |
||
:: Yes, but "port not specified" will typically mean "use the default port for that protocol" in any server that serves a single protocol. --[[User:Rdm|Rdm]] 00:19, 29 September 2011 (UTC) |
:: Yes, but "port not specified" will typically mean "use the default port for that protocol" in any server that serves a single protocol. --[[User:Rdm|Rdm]] 00:19, 29 September 2011 (UTC) |
||
::: More to the point, we're not talking about TCP or UDP, but IP. --[[User:Short Circuit|Michael Mol]] 13:56, 29 September 2011 (UTC) |
|||