|WikiProject Computing / Networking||(Rated Start-class, Low-importance)|
I suggest that Ip socket be merged into this article. It appears to be a stub covering the same subject. I plan to complete this merge by 2006-09-08 if there is no objection and/or a consensus is reached. -- Ratarsed 11:46, 29 August 2006 (UTC)
- Done -- Ratarsed 18:46, 12 September 2006 (UTC)
If this article is about IP sockets then the comment about SNA should be moved elsewhere. SNA only runs over DLSw on the Internet as it as its own lower level protocol. In addition there is not a clear definition here of a socket. Does it include the API? The queue? If there are multiple definitions they should be clearly identified and listed. The higher level definition of "socket" is in error by including "an end-point of a bi-directional communication link in the Berkeley sockets API". Pointing to a parent entity is not a valid definition. User:jbottoms76
Could someone go over the process an application might take in creating a socket -I'm interested in how port numbers are assigned in particular User:DragonSlayre12:14pm, 9 September 2007 (New Zealand time). —Preceding unsigned comment added by 126.96.36.199 (talk) 00:16, 9 September 2007 (UTC)
Missing references: The article does not refer to any API standard. There are some de facto standards for Berkely Sockets and WinSock.
Citations to RCF/STD are needed. For Example, RFC3493, R. Gilligan et al., “Basic Socket Interface Extensions for IPv6,” February 2003, http://www.rfc-editor.org/ discusses difference between v.4 and v.6 versions of the library. —Preceding unsigned comment added by 188.8.131.52 (talk) 04:22, 7 February 2010 (UTC)
This seems more like a Java tutorial on socket programming as opposed to an article in an encyclopaedia. --184.108.40.206 01:17, 9 November 2007 (UTC)
- Where did that Java code come from?--Adoniscik 04:45, 13 November 2007 (UTC)
Obviously, this article was extracted from a book or tutorial: "It also draws on other skills, such as multi-threaded programming, discussed in the next chapter. For now, we'll focus on a simple, bare-bones TCP server that executes as a single-threaded application" o.O "next chapter"??? :O --220.127.116.11 16:32, 14 November 2007 (UTC)
Should we rephrase this?
Hi, in the phrase "The server creates one socket for each client, and these sockets share the same local socket address."
Would it be more appropriate to write "The server creates one socket for each client, and these sockets share the same local IP address."?
Because if I understood correctly, the socket address is composed by IP:PORT, the server will create a new socket for each client, say, 10.0.0.1:10000, 10.0.0.1:10002, etc. This way the sockets created on the server would share the same IP address, but their socket addresses would be different.