Nice ! The locking system can be done directly in JS with messages. Another solution (which require a little more work) would be to implement the bakery's algorythm<http://en.wikipedia.org/wiki/Lamport%27s_bakery_algorithm> .
For pub/sub, you would need to add for each object a boolean for each process, saying if the process subscribes the object. On Tuesday, April 23, 2013 11:15:17 AM UTC+2, Jan Supuka wrote: > > I wrote a C/C++ binding of shared memory access from nodejs. > https://github.com/supipd/node-shm > Still work in progress (but working for me), maybe usefull, if bug or > suggestion, inform me. > > Exactly like a Simon wrote, already are here real cases for using shared > memory from node.js. > And potential concurrency issues (solvable) aren't reason to not use > shared memory. > Maybe bigger problem is "eventable" shared memory, something like "inform > me, when someting is changed". > In case of one process as central-shared-memory-manager can be there some > form of sending very small ((-: > TCP packet "Hey You, signed ChangeOfValue subscriptor, somebody changed > Your area of interest in SharedMemoryControlledByMe", > as source of change event, on which COV client read shared memory to > accept changes. > Instead of TCP sending potentially large amount of bytes, this event > system simple MUST be (and is) faster. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
