Re: [zeromq-dev] get socket condition

2014-08-11 Thread Goswin von Brederlow
On Mon, Aug 11, 2014 at 05:47:14PM +0800, bino oetomo wrote:
> Dear All,
> c/q Goswin von Brederlow .. Really appreciate your response
> On Mon, August 11, 2014 5:36 pm, Goswin von Brederlow wrote:
> > There are lots of ways the underlying tcp socket can die. But zeromq
> > will reconnect the socket again and again and again.
> >
> > Only problem is that you can loose messages when it dies with messages
> > in flight. Zeromq has reliable delivery (if a message arrives then it is
> > all of a message), not garanteed delivery.
> >
> 
> So . .For now .. all I need to concern is just the HWM ?
> 
> Sincerely
> -bino-

A PUSH socket will block when the HWM is reached or return EAGAIN with
ZMQ_DONTWAIT. Easy enough to handle.

MfG
Goswin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


Re: [zeromq-dev] get socket condition

2014-08-11 Thread bino oetomo
Dear All,
c/q Goswin von Brederlow .. Really appreciate your response
On Mon, August 11, 2014 5:36 pm, Goswin von Brederlow wrote:
> There are lots of ways the underlying tcp socket can die. But zeromq
> will reconnect the socket again and again and again.
>
> Only problem is that you can loose messages when it dies with messages
> in flight. Zeromq has reliable delivery (if a message arrives then it is
> all of a message), not garanteed delivery.
>

So . .For now .. all I need to concern is just the HWM ?

Sincerely
-bino-

___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


Re: [zeromq-dev] get socket condition

2014-08-11 Thread Goswin von Brederlow
On Mon, Aug 11, 2014 at 05:10:11PM +0800, bino oetomo wrote:
> 
> 
> Dear all ...
> 
> Let's say I (using python) have simple :
> 
> ctx = zmq.Context()
> socket=ctx.socket(zmq.PUSH)
> socket.setsockopt(zmq.SNDHWM, 10)
> socket.connect('tcp://127.0.0.1:9001')
> 
> I knew that when HWM reach, I'll get EAGAIN exception.
> 
> But, is there any posibilities that a socket is accidently/silenty
> crash/dead ?
> 
> If so ... what is the error code ?
> 
> Is there any docs that explain zmq.ZMQError ? I mean :
> - What error code (int)
> - What error name
> - Meaning of the error, or what caused the error ?
> 
> 
> Sincerely
> -bino-

There are lots of ways the underlying tcp socket can die. But zeromq
will reconnect the socket again and again and again.

Only problem is that you can loose messages when it dies with messages
in flight. Zeromq has reliable delivery (if a message arrives then it
is all of a message), not garanteed delivery.

MfG
Goswin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


[zeromq-dev] get socket condition

2014-08-11 Thread bino oetomo


Dear all ...

Let's say I (using python) have simple :

ctx = zmq.Context()
socket=ctx.socket(zmq.PUSH)
socket.setsockopt(zmq.SNDHWM, 10)
socket.connect('tcp://127.0.0.1:9001')

I knew that when HWM reach, I'll get EAGAIN exception.

But, is there any posibilities that a socket is accidently/silenty
crash/dead ?

If so ... what is the error code ?

Is there any docs that explain zmq.ZMQError ? I mean :
- What error code (int)
- What error name
- Meaning of the error, or what caused the error ?


Sincerely
-bino-


___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev