I’m hoping that some of you could give some insight into a method for doing what I’m going to try to explain below.
I have a situation in my qnx based project were I would like multiple processes to register with another process. (A multi to one relationship). During normal operations messages will be sent from this single higher level process down to the “many” lower level processes. So at startup I want to have the lower level processes send a pulse/event upto the “server”, for lack of a better term. Once the server gets the pulse I would like to to send a message down to the sender (client) of that pulse to request its file path. (Note: all processes in question are Resource Managers). Once the clients return their file paths then the server will in the future be able to communicate with all the clients.
I know the server/client nomenclature probably isn’t being used properly here, but I just needed to name the processes something
My dilema is that I don’t know how to send the appropriate information in the pulse/event to the server, for it to be able to respond to the clients. A pulse does have 32 bits for “data”, but I don’t know if there is anything that I could put in there that would work.
I have also read that there is a new async messaging system that is “experimental” in 6.3.0 (we are using 6.3.2a). My assumption is that these messages could contain enough data to allow me to send the filepath from the client to the server with a single async message. Any thoughts on any/all of this would be appriciated.