This reminds me of one of my favourite incidents, when TCP sockets finally "clicked." A TCP socket requires local-ip:local-port => remote-ip:remote-port. Your local port is ephemeral, the destination is probably meaningful.
-
Show this thread
-
This isn't like the OSI model which is meant to just model reality. TCP sockets have limits -- you can run out of them! localhost:23000 => google:443 is one, localhost:23001 => google:443 is another... but you can reuse ports. localhost:23000 => bing:443 is a new TCP socket!
2 replies 0 retweets 0 likesShow this thread -
Replying to @byronwolfman
Sir, I find that you are the rare species that understands that you can have two identical source ends so long as the destination is different
1 reply 0 retweets 1 like -
Replying to @synackpse
In that case
@mendel deserves a shoutout for a memorable lesson
1 reply 0 retweets 0 likes
Replying to @byronwolfman @synackpse
tuples tuples everywhere
11:56 AM - 10 Feb 2018
from Junction Area, Toronto
0 replies
0 retweets
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.