Re^3: Best method for maintaining a session ID across multiple threads

I guess I am using the term thread incorrectly

The generic term for a single instance in a cluster is 'node'.

So after more thought about it I am going to investigate writing something that can serve the sessionID to "processes" via a port.

Clustering software always has some form of message passing API that allows the processes to communicate.

A quick google suggests that GridEngine supports OpenMPI. You shouldn't need to be inventing a solution for this, just read the docs.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: Best method for maintaining a session ID across multiple threads

Replies are listed 'Best First'.
Re^4: Best method for maintaining a session ID across multiple threads by markdibley (Sexton) on Jul 11, 2013 at 09:34 UTC
I completely agree - I never invent a solution when there is an alternative, which is why I was asking for advice about existing solutions to the problem of maintaining a session ID. But OpenMPI appears to be an overly engineered solution for my requirements. If I had a week to learn and implement I might consider it, but thank you very much for your help and your suggestions.	[reply]