Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • I'll add #4 - write a server process to manage the data. The basic rule about multi-process software is that something (i.e. one process) has to be in charge of a shared resource. Commented Mar 11, 2010 at 20:40
  • Exactly. That was what I was aiming with the management process that will create the buffer, check how full it is, etc. Commented Mar 11, 2010 at 20:44
  • 1
    But if you have such a process, all issues of placement new, use of shared memory etc. go away. You of course have new interesting issues like how to talk to the server, but those are well understood in the biz. Commented Mar 11, 2010 at 20:51
  • Agree with @Neil, additionally you can pick up unexpected side-benefits too, like being able to spread your clients around to multiple machines. Commented Mar 11, 2010 at 20:57
  • Not an answer to your question, but have you considered using a pipe and letting the OS take care of the synchronization for you? Commented Mar 11, 2010 at 21:06