Re: [zeromq-dev] Sending image file in chunks on push-pull socket

2017-02-19 Thread Kevin Sapper
Hi Supraja, without any details I can only point you to the guide http://zguide.zeromq.org/page:all#Transferring-Files //Kevin On Mo, Feb 20, 2017 at 8:46 , Supraja Jayakumar wrote: An image file is transferred from zmq server to zmq client through push-pull

[zeromq-dev] Sending image file in chunks on push-pull socket

2017-02-19 Thread Supraja Jayakumar
An image file is transferred from zmq server to zmq client through push-pull socket chunk by chunk (in 1024 bytes). I do not get the last 9KB of any file i send as the incoming message length on the client side zmq pull socket is zero! Plaform: windows/0mq bindings/node.js/visual studio 2015/git

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread brunobodin .
Kevin, I would like to be able to leverage the change I did about the zsys_interface variable (https://github.com/zeromq/czmq/pull/1602) in a tagged release, but I am ok with Luca's answer and can wait for a couple of weeks. thanks for asking Bruno On Sun, Feb 19, 2017 at 1:50 PM, Kevin Sapper

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread Kevin Sapper
There changes to czmq since the last release are so minimal that it does not require a new release now IMO. @brunobodin: Is there a feature you like to use from czmq master? On So, Feb 19, 2017 at 1:45 , Luca Boccassi wrote: On Sun, 2017-02-19 at 08:48 +0100,

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread Luca Boccassi
On Sun, 2017-02-19 at 08:48 +0100, brunobodin . wrote: > Hi Luca > > Do you also plan to release a CZMQ version ? > > Regards > > Bruno Could do, but there's still a couple of issues with zbeacon + ipv6 linklocal that I'd like to iron out before that. Don't want to tag the repo with a

Re: [zeromq-dev] router socket hangs on write (was detecting dead MDP workers)

2017-02-19 Thread Gyorgy Szekely
Hi Luca, Unfortunately I'm not familiar with libzmq internals, so I can't decide whether or not EAGAIN is appropriate. But as a library user I expect either: sending a message on a mandatory router socket not to block when queue is below HWM -or- documentation explicitly stating that