Detect Disconnection events on SUB socket?

[ogabrielides]

How to detect Disconnection event on a PUB socket?

I used:

let mut monitor = socket.monitor(); and monitor.try_next() on a thread. The only event that I got is SocketEvent::Connected even if I manually stopped the Publisher side on purpose.

How to detect SocketEvent::Disconnected?

[Bombadad]

Hmm I'll have to try this out. I've been wanting to see if these work.

…

On Thu, Nov 14, 2024, 06:32 Odysseas Gabrielides ***@***.***> wrote: How to detect Disconnection event on a PUB socket? I used: let mut monitor = socket.monitor(); and monitor.try_next() on a thread. The only event that I got is SocketEvent::Connected even if I manually stopped the Publisher side on purpose. How to detect SocketEvent::Disconnected? — Reply to this email directly, view it on GitHub <#201>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEIQCA63DE54O6H73UJXNPL2ASC3TAVCNFSM6AAAAABRYVWNQSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY2TQNJUGU2DIMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ogabrielides]

@CableSynth Cool, let me know if you manage to do this

[jmcphers]

It looks like this might not be implemented? If you look at REP sockets, they send a Disconnected event to the monitor when the peer disconnects:

zmq.rs/src/rep.rs

Lines 93 to 98 in 07c65dc

	fn peer_disconnected(&self, peer_id: &PeerIdentity) {
	if let Some(monitor) = self.monitor().lock().as_mut() {
	let _ = monitor.try_send(SocketEvent::Disconnected(peer_id.clone()));
	}
	self.peers.remove(peer_id);
	}

However, SUB sockets do not do this.

zmq.rs/src/sub.rs

Lines 110 to 112 in 07c65dc

	fn peer_disconnected(&self, peer_id: &PeerIdentity) {
	self.peers.remove(peer_id);
	}

I'm not a ZeroMQ expert but this may just be an oversight.

[WillPCowan]

Also haven't found a way to get a subscriber to understand that a publisher has disconnected. I can make an application level solution but this would only work if the publisher gracefully shuts down...

This is essential for implementing robust services/applications so priority should be high imo; I need this ASAP so could try and contribute but don't see any guidelines/support docs? (I guess the answer is just to get stuck in)

[gvz]

The same issue exist on PUB sockets.
I am working on a PR.

[rgbkrk]

Is this something which is better supported by using xpub and xsub?