| |||||||||||||
LCE: The failure of operating systems and how we can fix itLCE: The failure of operating systems and how we can fix itPosted Nov 15, 2012 9:55 UTC (Thu) by robert_s (subscriber, #42402)In reply to: LCE: The failure of operating systems and how we can fix it by epa Parent article: LCE: The failure of operating systems and how we can fix it
"it works out more robust this way."
Only because so far, little communication & cooperation between these appliances has been sought or required. If "appliances" are our new "processes" the fun is going to come when the equivalent of IPC is required.
And let's not even start talking about efficiency.
(Log in to post comments)
LCE: The failure of operating systems and how we can fix it Posted Nov 15, 2012 9:58 UTC (Thu) by epa (subscriber, #39769) [Link]
For better or worse inter-application communication will end up as being TCP/IP rather than via the filesystem or local IPC mechanisms.
LCE: The failure of operating systems and how we can fix it Posted Nov 15, 2012 16:04 UTC (Thu) by k3ninho (subscriber, #50375) [Link]
TCP/IP? That's a little broad: JSON via HTTP requests on port 80 (it's left to the reader to provide an insecure implementation via HTTPS/443).
LCE: The failure of operating systems and how we can fix it Posted Nov 22, 2012 6:08 UTC (Thu) by HelloWorld (guest, #56129) [Link]
What's the problem with IPC? The whole point of containers is to have better granularity: share the IPC namespace, but don't share the file system namespace so that you can use your own shared libraries.
LCE: The failure of operating systems and how we can fix it Posted Nov 22, 2012 8:13 UTC (Thu) by Fowl (subscriber, #65667) [Link]
Shared libraries often use IPC...
Plus people want to use containers for more serious "untrusted" isolation.
|
|||||||||||||