You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2019. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: