Quote:
Originally Posted by penquin.toes
I realize it may be a figure it out for yourself mindset for you but I've literally only been self reading this trying to understand the material for a matter of days.
...My journey continues
|
My response to you
wasn't a "blow-off."
The point of your self-appointed exercise
must be: "to figure it out for yourself."
Find a description of each of these four services, and ask yourself repeatedly this question:
"does the job-description of this particular service indicate that it accepts and responds to requests from 'the outside world any computer other than itself?'"
Again, my response (and other responses like it) is not a blow-off, and there's
not one single person here who does not instantly recognize and appreciate how difficult-to-grok this stuff actually is. However, "when you are swimming in the sea of computers, you risk drowning in
details," and what saves you is: "getting the
big picture." Translating the question into a process for interpreting it.
Incidentally, there's a certain amount of
ambiguity in this question: there are "service-provider" services, and there are sometimes "service-client" services. (For instance, anytime you're connected to a wireless network that's secured by a real-world password protocol, you've got a little service running on your machine which re-negotiates the cipher session-key every hour or so. Since it runs independently, it qualifies as a "service," but it doesn't accept outside connections.)
The same bright-line rules apply to Windows, Linux, Android, iPhone, and ...
everything else. "Terminology: different. Basic ideas: the same."
