[zeromq-dev] Problem: ipc:// does not work on Windows

Doron Somech somdoron at gmail.com
Thu Oct 2 17:32:14 CEST 2014

I would go with mutex and shared file, but I think it is complicated to
implement, because every time socket connects it has to check the file and
cannot actually use hashing. The problems with hashing:

* Try to bind and port is taken ?
* Try to connect but the peer is not zeromq
* Try to connect and the peer is zeromq but not the one I actually want.

Because of the third problem we will have to check the file on every
connect which mean we don't need the hashing, just the file.

So we have a file, every time we bind we bind to ephemeral port and write a
row to the file with the port and the name and every time we connect we
check the file, but the remain case is when do we clear the file?

On Thu, Oct 2, 2014 at 3:12 PM, Pieter Hintjens <ph at imatix.com> wrote:

> This is annoying mainly because it hurts code portability and also
> because ipc:// (especially with abstract endpoints) is a nicer
> semantic for local services than TCP ports. e.g. I've a protocol
> called zccp and the default location for a zccp broker is
> ipc://@/zccp.
> Solution: cheat, on Windows
> Real solution: accept "ipc://" endpoints and hash them to a socket
> number in the ephemeral range, then bind/connect on with
> that port number.
> Difficulty: hash conflicts. :-)
> If anyone has a plausible solution to hash conflicts (registry?) then
> this should be quite simple to make.
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20141002/cb08ecaf/attachment.htm>

More information about the zeromq-dev mailing list