Local Inter-Process Communication: Difference between revisions

Revision as of 21:02, 19 August 2012

Revision as of 06:14, 7 May 2014

Line 2:

The (A)LPC interface is part of Windows NT's undocumented [[Native API]], and as such is not available to applications for direct use. However, it can be used indirectly in the following instances:

* when using the [[Remote ProcedureMicrosoft CallRPC]] API to communicate locally, i.e. between the processes on the same machine

* by calling Windows API which use (A)LPC (see below)

Line 28:

The [[Local Security Authority Subsystem Service]] (LSASS), [[Session Manager]] (SMSS), and [[Service Control Manager]] all use (A)LPC ports directly to communicate with client processes. [[Winlogon]] and the [[Reference monitor|Security Reference Monitor]] use it to communicate with the LSASS process.

As mentioned, Microsoft RPC can use (A)LPC as a transport when the client and server are both on the same machine. Many services that are designed to communicate only on the local computer use (A)LPC as the only transport through RPC. The implementation of remote [[object linking and embedding|OLE]] and [[Distributed Component Object Model|DCOM]] in many cases uses (A)LPC for local communication as well.

==See also==