On 03/22/2011 04:13 AM, Marcelo Cantos wrote:
1. MartinS: For the same reasons that MartinL highlights, I don't see
a file-dump working. In addition, how does a connecting peer know
which port to connect to if the binding peer hasn't fired up yet?
If the connecting peer
Hi Marcelo,
2011/3/22 Marcelo Cantos marcelo.can...@gmail.com:
MartinL: The zpmd solution doesn't require a service. Erlang nodes start
epmd on-the-fly when they detect that it isn't running, and it runs forever
from that point on. This does, of course, require a zpmd.exe to be sitting
marcelo.can...@gmail.com said:
2. MartinL: The zpmd solution doesn't require a service. Erlang nodes start
epmd on-the-fly when they detect that it isn't running, and it runs
forever
from that point on. This does, of course, require a zpmd.exe to be sitting
around in easy reach,
Thank you for the replies, MartinL and MartinS. I'll bulk up my responses
for simplicity:
1. MartinS: For the same reasons that MartinL highlights, I don't see a
file-dump working. In addition, how does a connecting peer know which port
to connect to if the binding peer hasn't fired up
sust...@250bpm.com said:
On 03/18/2011 02:09 PM, Martin Lucina wrote:
What do you think? This approach would provide the name lookup without the
need for any external service.
Why not simply write auto-generated port number to the file provided in
the connection string? The other peer
Hi Marcelo,
marcelo.can...@gmail.com said:
I've been mulling over the Windows ipc problem and it occurred to me that
Erlang solves a very similar problem (allowing nodes to talk to each other)
essentially using option 4 with a helper program, called epmd (Erlang Port
Mapper Daemon). epmd
On 03/18/2011 02:09 PM, Martin Lucina wrote:
What do you think? This approach would provide the name lookup without the
need for any external service.
Why not simply write auto-generated port number to the file provided in
the connection string? The other peer would then simply read the port
Hi Marcelo,
In ZeroMQ, this might work by having a process (zpmd?) is responsible
for binding to dynamic port numbers for use by the ipc transport, and
which hands the port over to the server process — when it turns up — via
a call to WSADuplicateSocket(). Any ZMQ process trying to use ipc
I've been mulling over the Windows ipc problem and it occurred to me that
Erlang solves a very similar problem (allowing nodes to talk to each other)
essentially using option 4 with a helper program, called epmd (Erlang Port
Mapper Daemon). epmd accepts requests to associate a name with a port,
A couple of qualifiers:
1. I meant to say that this proposed solution wouldn't intrude *deeply* into
the ZMQ library. It will obviously intrude a little.
2. I just noticed that there has been some discussion about getting IPC
working on Windows using intern-power at GSoC. If there is
On 11/30/2010 03:51 PM, Martin Lucina wrote:
marcelo.can...@gmail.com said:
2010/10/28 Mikael Helbo Kjærm...@designtech.dk
... I could really use an IPC solution for Windows. ...
I would love to see this too. I understand that the problems with
implementing
IPC on Windows are
On 30 November 2010 15:57, Sven Koebnick sven.koebn...@t-online.de wrote:
a few years ago, I read some artical about cheating IPC into Windows. it
worked with using parts of the paging file as a shared datafile and thereby
simulating shared memory.
Maybe this can be wrapped to just plug it
marcelo.can...@gmail.com said:
2010/10/28 Mikael Helbo Kjær m...@designtech.dk
... I could really use an IPC solution for Windows. ...
I would love to see this too. I understand that the problems with implementing
IPC on Windows are significant, so I am trying to decide between
-
E = mc² ± 2dBA - everything is relative
-
-Original Message-
Date: Tue, 30 Nov 2010 06:05:21 +0100
Subject: [zeromq-dev] IPC on Windows (again)
From: Marcelo Cantos marcelo.can...@gmail.com
14 matches
Mail list logo
