Martin,
On Wed, Jan 26, 2011 at 11:42 PM, Martin Sustrik sust...@250bpm.com wrote:
Hi David,
My quick fix was to check the address and interface in
socket_base::bind() and socket_base::connect().
I've pasted my change below in case you want to do something similar.
The real solution
On 01/27/2011 09:28 AM, David Kantowitz wrote:
The real solution IMO would be to introduce a new address
structure that would contain the address as such, with no elements
to resolve.
When will sockaddr_storage be insufficient?
We have following transports that have to be taken
On Thu, Jan 27, 2011 at 12:44 AM, Martin Sustrik sust...@250bpm.com wrote:
On 01/27/2011 09:28 AM, David Kantowitz wrote:
The real solution IMO would be to introduce a new address
structure that would contain the address as such, with no elements
to resolve.
When will
On 01/27/2011 09:51 AM, David Kantowitz wrote:
Is it really that bad to parse and process the transport URL twice?
1. I'd guess (but I'm not sure) most applications don't call
connect() very often.
2. The bind library probably cached the name lookup.
The problem is what to do if the
On Wed, Jan 26, 2011 at 6:53 PM, David Kantowitz dkantow...@gmail.comwrote:
Hello Joshua,
I had similar problems. I get an assertion on an i/o thread anytime I
called connect() to a malformed or unresolvable address, and bind() to an
unknown or malformed interface.
I think in part this
Joshua,
I am trying to setup a service with ZeroMQ that subscribes to a TCP
endpoint that doesn't exist when the computer starts up. I am using the
computer name as I don't know what the DHCP address will be. ZMQ crashes
with the following assertion: Assertion failed: rc == 0
I am trying to setup a service with ZeroMQ that subscribes to a TCP
endpoint that doesn't exist when the computer starts up. I am using the
computer name as I don't know what the DHCP address will be. ZMQ crashes
with the following assertion: Assertion failed: rc == 0
