Talk:Network socket: Difference between revisions

Content deleted Content added

Inline

Revision as of 07:47, 21 January 2015

Computing: Networking Start‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by Networking task force (assessed as Mid-importance).

Template:Findsourcesnotice

Suggested merge

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)[reply]

Done -- Ratarsed 18:46, 12 September 2006 (UTC)[reply]

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

Request

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 124.197.57.56 (talk) 00:16, 9 September 2007 (UTC)[reply]

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 67.173.186.180 (talk) 04:22, 7 February 2010 (UTC)[reply]

Article Quality

This seems more like a Java tutorial on socket programming as opposed to an article in an encyclopaedia. --121.45.19.162 01:17, 9 November 2007 (UTC)[reply]

Where did that Java code come from?--Adoniscik 04:45, 13 November 2007 (UTC)[reply]

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 --200.17.143.33 16:32, 14 November 2007 (UTC)[reply]

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.

Anyone agrees? — Preceding unsigned comment added by Bnegrao2 (talk • contribs) 20:37, 19 January 2013 (UTC)[reply]

@@ Line 30: / Line 30: @@
 Anyone agrees?  <small><span class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Bnegrao2|Bnegrao2]] ([[User talk:Bnegrao2|talk]] • [[Special:Contributions/Bnegrao2|contribs]]) 20:37, 19 January 2013 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
-I find the description at the beginning of the Overview section a bit confusing:
-"An Internet socket is characterized by a unique combination of the following :
-* Local socket address: ...
-* Remote socket address: ...
-* Protocol..."
-The reason I find it confusing is that it does not distinct well enough between the natural characteristics of any socket, being an '''end point''', meaning having ''local socket address'' and ''protocol'', and the special case when a socket is connected to a remote end-point, in which case it has the knowledge of the ''remote socket address''.
-Therefore, I would like to suggest the following rephrasing of the first 2 sub-sections of the overview section:
-"An Internet socket is characterized by the following:
-*Local socket address: Local IP address and port number,
-*[[Protocol (computing)|Protocol]]: A transport protocol (e.g., [[Transmission Control Protocol|TCP]], [[User Datagram Protocol|UDP]], [[raw socket|raw IP]], or others). TCP port 53 and UDP port 53 are consequently different, distinct sockets.
-A TCP socket that has been connected to another socket, e.g. during the establishment of a TCP connection, will also be characterized by a remote socket address. As discussed in the client-server section below, this is necessary since a TCP server may serve several clients concurrently. The server creates one socket for each client, and these sockets share the same local socket address from the point of view of the TCP server."
-Any thoughts? [[User:Ronny Weisman|Ronny Weisman]] ([[User talk:Ronny Weisman|talk]]) 07:43, 21 January 2015 (UTC)