Local Inter-Process Communication: Difference between revisions

Revision as of 21:16, 16 July 2009

Revision as of 21:16, 16 July 2009

Line 1:

The '''local procedure call''' ('''LPC''', often also referred to as '''lightweight procedure call''') facility is a service provided by the [[Microsoft]] [[Windows NT]] [[Kernel (computer science)|kernel]] for light weight [[message queue]] between [[process (computing)|process]]es on the same computer. The LPC interface is part of Windows NT's undocumented [[Native API]], although it can be used indirectly in applications via the documented [[remote procedure call]] system using the NCALRPC transport (which is implemented by LPC).

== Implementation ==

LPC is implemented using kernel "port" objects. A server process first creates a port object with a well known name, and waits for clients to connect. A client process then connects by opening that port and sending a connect message. If the server accepts the connection, a new unnamed port object is created for the connection. Port objects are securable kernel objects that allow a process to identify the process on the other side of the connection.

Line 17:

==See also==

* [[Doors (computing)|Doors]]

== References ==

* Prasad Dabak, Milind Borate, Sandeep Phadke. ''Undocumented Windows NT.'' [[Hungry Minds]], 1999. ISBN 0-7645-4569-8

* David A. Solomon, Mark E. Russinovich. ''Inside Windows 2000.'' Microsoft Press. ISBN 0-7356-1021-5

== External links ==

* [http://www.windowsitlibrary.com/Content/356/08/toc.html Local Procedure Call] - Includes explanation of undocumented functions

* [http://www.zezula.net/en/prog/lpc.html LPC Communication]