Confirmed users
158
edits
Multiprocess Images: Difference between revisions
→Issues and Questions
| Line 47: | Line 47: | ||
* If a content process goes down, are we guaranteed by the IPC mechanism to hear about it? If not, what do we do when a client goes down without releasing the proxy hold on an image in the server cache? | * If a content process goes down, are we guaranteed by the IPC mechanism to hear about it? If not, what do we do when a client goes down without releasing the proxy hold on an image in the server cache? | ||
* How does all this fit into the existing security architecture? | * How does all this fit into the existing security architecture? | ||
* Do we want to map the shmem regions individually or use one big region? | * Do we want to map the shmem regions individually or use one big region? | ||
** Is it a violation of the eventual security model if one content process can read (not write) the image data of other processes? This would effectively nix the one-big-region strategy. | ** Is it a violation of the eventual security model if one content process can read (not write) the image data of other processes? This would effectively nix the one-big-region strategy. | ||