Skip to main content
Unix & Linux

Return to Question

Post Undeleted by CommunityBot
Post Deleted by CommunityBot
deleted 81 characters in body
Source Link
user149572
user149572

I understand that the term "socket" can mean two different things in the Unix/Linux context:

  • A Unix socket; the interface between 2 or more processes. An example is a CGI that comes between a webserver and other processes like PHP.
  • An IP socket; the interface between a process and 1 or more communicating services (or machines).

Is the general definition sums up in these two or there are is more to "socket" in our context?

I understand that the term "socket" can mean two different things in the Unix/Linux context:

  • A Unix socket; the interface between 2 or more processes. An example is a CGI that comes between a webserver and other processes like PHP.
  • An IP socket; the interface between a process and 1 or more communicating services (or machines).

Is the general definition sums up in these two or there are is more to "socket" in our context?

I understand that the term "socket" can mean two different things in the Unix/Linux context:

  • A Unix socket; the interface between 2 or more processes.
  • An IP socket; the interface between a process and 1 or more communicating services (or machines).

Is the general definition sums up in these two or there are is more to "socket" in our context?

Source Link
user149572
user149572

Understanding the term "socket" in the Unix/Linux context

I understand that the term "socket" can mean two different things in the Unix/Linux context:

  • A Unix socket; the interface between 2 or more processes. An example is a CGI that comes between a webserver and other processes like PHP.
  • An IP socket; the interface between a process and 1 or more communicating services (or machines).

Is the general definition sums up in these two or there are is more to "socket" in our context?