Hi
I've worked a bit with some of these techniques and asked around to several people I know locally and they all believe in using Shared Memory for larger messages and named pipes for smaller ones. One guy recommended a solution of having a shared memory block for the messages, creating an index on it and sending the index key over a named pipe for retrieval by the recipient. But I am fairly certain he is using Boost::Interprocess for it so that is maybe not useful. I've so far gotten by with a Shared Memory solution (and it is very fast so far), but the locking has been hard to make work. I miss domain sockets on Windows ;) Regards, Mikael I found an amusing list of IPC methods on Windows from MSDN, · Clipboard <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_the_clipboard_for_ipc> · COM <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_com_for_ipc> · Data Copy <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_data_copy_for_ipc> · DDE <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_dde_for_ipc> · File Mapping <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_a_file_mapping_for_ipc> · Mailslots <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_a_mailslot_for_ipc> · Pipes <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_pipes_for_ipc> · RPC <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_rpc_for_ipc> · Windows Sockets <http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx#base.using_windows_sockets_for_ipc> http://msdn.microsoft.com/en-us/library/aa365574(VS.85).aspx It would probably be worth investigating shared memory (File Mapping) or named pipes for content and a Windows Socket for synchronisation. -- Steve-o
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
