The heartbeats are an interesting problem. I haven't yet made my mind about them. AFAICT the only real use cases for heartbeats is in high-availability systems to initiate fail-over.
Btw, have a look at the thread I've started at IETF mailing list. You may want to comment: http://www.ietf.org/mail-archive/web/ietf/current/msg62134.html Martin Brian Granger wrote: > I plan on creating a new device for heartbeating in 0MQ. I am focused > on other 0Mq things right now, but it shouldn't be too difficult given > the new device API. The only difference is that a heartbeat device > would only take 1 socket. > > Cheers, > > Brian > > On Mon, Jul 5, 2010 at 9:39 AM, Sarat K <[email protected]> wrote: >> Hi, >> I am exploring ZeroMq for one of my application. One of the requirement I >> have is to get disconnect notification from the ZeroMQ kernel when ever a >> client terminates the connection/when ever client program crashes I wanted >> to know about the disconnect in the communication. My application model is; >> I have a single server that is connected to many clients and server wants to >> know when ever a client got disconnected. >> I have come across few examples like using gap_message or registering an >> error handler using zmq::set_error_handler api. But it seems the interface >> has been change since these examples were listed, I dont find any thing in >> the current interface which satisfies my requirement. >> I greatly appreciate any help here. >> Thanks >> sk >> >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> > > > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
