site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hi, Thanks _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I'm trying to use MIG generated RPC between 2 threads inside a *same* process as a "pracical" way for a thread to notify another one. The idea was to have one thread send a message to the other one without the need for an intermediate lock-free fifo for example. Basically I'm using the client logic inside the server : accessing the RPC port that is published by the server and using RPC call on this port from one thread to be handled by another "listening" thread. I had to hack the MIG generated files to avoid names conflict (the same RPC call that is usually compiled on server and client side independently is now compiled on the server side). Even if it seems to work correctly, I was wondering if is is correct to use MIG RPC system like that or if another light inter-thread communication system should be used. Stephane Letz This email sent to site_archiver@lists.apple.com