What is the best practice for managing ABI changes to process-shared-memory-data during library upgrades?
-
-
What do you replace it with? A pipe or socket and a message based protocol?
-
Depends on what the usage case is. A message based protocol is easier to version, and harder to corrupt, than shared memory, tho.
-
Every use case for shared memory is about raw inter-process performance. Shared ring buffers. Shared data. etc.
-
Not always; nscd doesn't strike me as such a case. It strikes me as silly premature optimization.
-
I have not evaluated the case for nscd's use of a shared map, but I agree that it is complex and difficult to audit.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.