Difference between UDP socket and TCP socket number of connections
up vote
0
down vote
favorite
Since UDP sockets are identified by (dst IP, dst Port), is it correct to assume that a client can only send packets through one UDP socket to a particular application process ( assuming the application process uses one port ) running on the server side ? Whereas in TCP, because TCP sockets can be identified by (src IP , src port , dst IP , dst port ), there can be multiple TCP connections to the same dst port on the server side, with each TCP socket on the client side using a different source port. Hope this question doesnt sound weird.
sockets networking udp
asked Nov 19 at 16:00
calveeen
6611
add a comment |
up vote
0
down vote
favorite
Since UDP sockets are identified by (dst IP, dst Port), is it correct to assume that a client can only send packets through one UDP socket to a particular application process ( assuming the application process uses one port ) running on the server side ? Whereas in TCP, because TCP sockets can be identified by (src IP , src port , dst IP , dst port ), there can be multiple TCP connections to the same dst port on the server side, with each TCP socket on the client side using a different source port. Hope this question doesnt sound weird.
sockets networking udp
asked Nov 19 at 16:00
calveeen
6611
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Since UDP sockets are identified by (dst IP, dst Port), is it correct to assume that a client can only send packets through one UDP socket to a particular application process ( assuming the application process uses one port ) running on the server side ? Whereas in TCP, because TCP sockets can be identified by (src IP , src port , dst IP , dst port ), there can be multiple TCP connections to the same dst port on the server side, with each TCP socket on the client side using a different source port. Hope this question doesnt sound weird.
sockets networking udp
asked Nov 19 at 16:00
calveeen
6611
Since UDP sockets are identified by (dst IP, dst Port), is it correct to assume that a client can only send packets through one UDP socket to a particular application process ( assuming the application process uses one port ) running on the server side ? Whereas in TCP, because TCP sockets can be identified by (src IP , src port , dst IP , dst port ), there can be multiple TCP connections to the same dst port on the server side, with each TCP socket on the client side using a different source port. Hope this question doesnt sound weird.
sockets networking udp
sockets networking udp
asked Nov 19 at 16:00
calveeen
6611
asked Nov 19 at 16:00
calveeen
6611
asked Nov 19 at 16:00
calveeen
6611
asked Nov 19 at 16:00
calveeen
6611
asked Nov 19 at 16:00
calveeen
6611
6611
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00
add a comment |
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378432%2fdifference-between-udp-socket-and-tcp-socket-number-of-connections%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The number of connections would certainly be different because UDP does not use connections, and it it will always have no connections, but TCP only uses connections. See this answer.
– Ron Maupin
Nov 19 at 16:11
I think that is basically correct. I'm not sure if there is a practical difference though.
– James K Polk
Nov 19 at 17:00