Nothing too magical about it. Any program can listen on any port it wants. Some ports are standardized, but doesn't stop a program from listening on those ports anyway. Like web browsers always use 80 (and redirected to 443 if https is required).
-
-
Fair. Would "it's a persistent identifier that enables routing within a machine" be what you're looking for? There's not a lot to formally define; they're routing numbers that, unlike IP addresses, don't require negotiation or cooperation between systems
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hi :) http://www.ece.virginia.edu/cheetah/documents/papers/TCPlinux.pdf … seems to refer to buffers which are being sent / read to, so I guess a port would be a file handle so there are 65535 pointers in an array. I'd probably pick a hashmap to mark which pid "reserved" a port. I wonder if
@b0rk has already written bout itThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.