Choose your poison: http://msdn.microsoft.com/en-us/library/aa365574%28VS.85%29.aspx The following IPC mechanisms are supported by Windows: Clipboard COM Data Copy DDE File Mapping Mailslots Pipes RPC Windows Sockets The closest to DBus is COM.
First, remember the goal of these ‘synchronizing objects’ : These objects were designed to provide an efficient and coherent use of ‘shared data’ between more than 1 thread among 1 process or from different processes. These objects can be ‘acquired’ or ‘released’. That is it!!! End of story!!! Now, if it helps to you, let … Read more
You can just do it. { local @ARGV = qw<param1 param2 param3>; do ‘/home/buddy/myscript.pl’; } Prevents the overhead of loading in another copy of perl.
I am currently looking into the same questions. For me the possibility of adding Windows clients later makes the situation more complicated; in your case the answer seems to be simpler. About the options you have considered: Control files: While it is possible to communicate via control files, you have to keep in mind that … Read more
Native objects don’t get shared between processes (due to reference counting). Instead, you can pickle them and share them using unix domain sockets, mmap, zeromq, or an intermediary such a sqlite3 that is designed for concurrent accesses.
I found out how to do it. It is not about threads, and not about select(). When I run the first process (grep), it creates two low-level file descriptors, one for each pipe. Lets call those a and b. When I run the second process, b gets passed to cut sdtin. But there is a … Read more
Short answer: RPC is the protocol. The socket provides access to the transport to implement that protocol. RPC is the service and protocol offered by the operating system to allow code to be triggered for running by a remote application. It has a defined protocol by which procedures or objects can be accessed by another … Read more
ReadProcessMemory shouldn’t even be listed as an IPC method; yes, it can be used as such, but it exists mainly for debugging purposes (if you check its reference, it’s under the category “Debugging functions”), and it’s surely slower than “real” shared memory because it copies the memory of a process into the specified buffer, while … Read more
I could successfully handle the (almost) same issue as yours doing the following: In your Class : ServiceBase, that represents your Service class, you might have: public Class () //constructor, to create your log repository { InitializeComponent(); if (!System.Diagnostics.EventLog.SourceExists(“YOURSource”)) { System.Diagnostics.EventLog.CreateEventSource( “YOURSource”, “YOURLog”); } eventLog1.Source = “YOURSource”; eventLog1.Log = “YOURLog”; } Now, implement: protected override … Read more
You can use socketpair only where you create both processes, like so: call socketpair – now you have two socket file descriptors (two ends of a single pipe) nominate one end to be the parent and one to be the child end. It doesn’t matter which, just make a choice and stick to it later … Read more