Sure, you can..... the number can still be stored on one master machine in shared mem, controlled by a daemon, and have the daemon listen for external socket connections. The program can run over the socket.
| [reply] |
You know as well as I do that that is not what is generally meant by sharing data using shared memory. Yes, technically shared memory is used, but what enables sharing is the client/server setup. Which takes a lot of work and doesn't change much whether or not it uses shared memory.
| [reply] |
You know as well as I do
With the lack of details by the OP, I can envision a typical setup like this: the master machine, say at a University, is the primary machine to run the software on. People can ssh into it, or run at a console. It is the primary way to run the software, and uses shared memory segments for speed. To extend the capabilities to those on the road, a secondary access method is used thru a daemon that accesses both the shared memory and a socket...... very typical setup in my opinion.
| [reply] |