Revision as of 20:36, 18 February 2022 edit Citation bot (talk \| contribs) Bots 5,866,893 edits Alter: isbn. Upgrade ISBN10 to 13. \| Use this bot. Report bugs. \| Suggested by Whoop whoop pull up \| Category:Windows communication and services \| #UCB_Category 19/59 ← Previous edit		Revision as of 01:39, 12 March 2023 edit undo Bumm13 (talk \| contribs) Administrators 79,764 edits m →Implementation: punctuation fix Next edit →
Line 6: ==Implementation== (A)LPC is implemented using kernel "port" objects, which are securable (with [[Access -control list\|ACL]]s, allowing e.g. only specific [[Security Identifier\|SID]]s to use them) and allow identification of the process on the other side of the connection. Individual messages are also securable: applications can set per-message SIDs, and also test for changes of the security context in the token associated with the (A)LPC message. The typical communication scenario between the server and the client is as follows:

Local Inter-Process Communication: Difference between revisions