Skip to content
This repository has been archived by the owner on Mar 4, 2019. It is now read-only.

Support interprocess communication perimeter #4

Open
HadrienG2 opened this issue Mar 16, 2017 · 0 comments
Open

Support interprocess communication perimeter #4

HadrienG2 opened this issue Mar 16, 2017 · 0 comments

Comments

@HadrienG2
Copy link
Owner

Sometimes, it makes sense to implement the client and the server of an asynchronous operation in different OS processes. Although shared-memory communication can still easily be used, the interprocess communication setting still has a number of unique points that should be carefully considered:

  • Processes can crash independently and should tolerate each other's failure
  • Processes live in separate address spaces, so pointers should be used sparingly in communication
  • Processes are isolated from each other for a reason, security considerations should be examined
  • Interprocess signaling is more complex and less efficient than thread signaling
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant