After that, it can be as simple as just a chat client passing plain text back and forth.
-
-
Replying to @PlainOldWaffles @BerzerkerBuilds
No I know but how do the integers map? Is it a hashmap implementation, what do they do under the hood when you specify e.g. port 8888
2 replies 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
Hmm. Not sure what you mean exactly then, my apologies. It's not exactly mapping, you just tell your program what port to listen on. If you tell it to listen on 80 and point a web browser to localhost, your web browser will then be talking with your program.
1 reply 1 retweet 0 likes -
Replying to @PlainOldWaffles @BerzerkerBuilds
Yes I know that but what does the 80 *do* that 79 *doesn’t*
1 reply 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
Absolutely nothing :) That's the beauty. Ever use a web browser to connect to your home router on port 8080? Functionally identical to Port 80, they just use 8080 so as not to conflict with anything listening on 80
2 replies 0 retweets 0 likes -
The port numbers themselves are meaningless. There are standard ports. Like again 80 and 443, etc. But ANY program can take over that port and do it's own thing. It's not the port that determines the protocol
1 reply 0 retweets 0 likes -
Replying to @PlainOldWaffles @BerzerkerBuilds
Lemme phrase it like this: # If I expose only port 4500 on a host, and try to send a request on 4600, I will get no response. Where does the machinery lie that allows the host to ignore the request on 4600?
1 reply 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
You have to have some program running on that PC that opens a listening socket on any given port. Then that program literally just sits there running waiting for something to connect in that port. If you don't have any server programs running, there won't be any ports listening
2 replies 0 retweets 0 likes -
Replying to @PlainOldWaffles @BerzerkerBuilds
How does the server software know to reject a request coming in on a port that’s not open. Is the port number encoded in the packet?etc. Again, I know what ports are but not how they get implemented on the transport layer
3 replies 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
It doesn't. It is only aware of the ports it's listening on. Everything else by default is just not opened. I guess think of it like a wall? By default no way to get through that wall. Something has to poke a hole through it? Terrible analogy ... :)
1 reply 0 retweets 0 likes
I know it’s like a wall. I’m asking what the wall is made of
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.