March 16, 2019 
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >
March 16, 2019 [04:34:02] *** Flash <Flash!~flash@c-73-34-45-134.hsd1.co.comcast.net> has joined #zeromq[05:32:05] *** guido_g <guido_g!~guido_g@ip1f103f9c.dynamic.kabel-deutschland.de> has quit IRC (Read error: Connection reset by peer)[05:34:08] *** guido_g <guido_g!~guido_g@ip1f103f9c.dynamic.kabel-deutschland.de> has joined #zeromq[06:32:23] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has joined #zeromq[06:45:12] *** Shio_1 <Shio_1!~Thunderbi@151.100.wtt.p2wt.com> has joined #zeromq[06:45:27] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has quit IRC (Ping timeout: 246 seconds)[06:50:11] *** Shio_1 <Shio_1!~Thunderbi@151.100.wtt.p2wt.com> has quit IRC (Ping timeout: 268 seconds)[07:10:55] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has joined #zeromq[07:18:39] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has quit IRC (Remote host closed the connection)[07:26:24] *** cognifloyd <cognifloyd!~cognifloy@072-191-249-006.res.spectrum.com> has quit IRC (Ping timeout: 246 seconds)[09:15:44] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has joined #zeromq[09:19:57] *** Shio_ <Shio_!~Thunderbi@151.100.wtt.p2wt.com> has quit IRC (Ping timeout: 244 seconds)[11:07:30] *** diorcety <diorcety!~diorcet@176-144-97-78.abo.bbox.fr> has joined #zeromq[15:38:35] *** cognifloyd <cognifloyd!~cognifloy@072-191-249-006.res.spectrum.com> has joined #zeromq[16:32:44] *** afighttilldeath[ <afighttilldeath[!afighttill@gateway/shell/matrix.org/x-cinusonthgfukhin> has quit IRC (Write error: Broken pipe)[16:42:23] *** afighttilldeath[ <afighttilldeath[!afighttill@gateway/shell/matrix.org/x-hwmkuedcibjyaylw> has joined #zeromq[20:48:28] *** marijnfs <marijnfs!~marijnfs@D9797263.cm-3-2b.dynamic.ziggo.nl> has joined #zeromq[21:00:08] *** diorcety <diorcety!~diorcet@176-144-97-78.abo.bbox.fr> has quit IRC (Read error: Connection reset by peer)[21:01:26] <marijnfs> Hi, I'm trying to make network discovery with zeromq. So I want to detect which IP is connecting to a socket.[21:02:25] <marijnfs> I see an engine gets a peer_addres, and in the in_event on the tcp_listener i can get the ip from that, but not sure how to integrate the into my program[21:19:07] <bv> I'm using Zyre for discovery and publish in Zyre's key/value headers each bind'ed socket "name" as the key and the endpoint as the value. Then, other peers can do pattern matching on the socket "name" to see if they want to connect().[21:20:36] <bv> but, my idea of "discovery" sounds a bit different from what you describe so I'm not sure if this is in the direction you are asking.[22:28:25] <marijnfs> bv: thanks, i'll check out zyre![22:29:26] <marijnfs> i remember checking it out years ago, did it evolve a lot?[22:30:09] <bv> I don't have the experience to know.[22:32:08] <bv> I do know that the zproto_peer_c.gsl example in zproto is broken due to changes in Zyre. I have a rewritten version it if there's interest. it probably needs more work but it has at least as much functionality as the old one meant to have.[22:32:47] <bv> you don't need zproto for Zyre, but just in case you go that route and find that, I mention it. I lost some time trying to make it work.[23:12:38] *** marijnfs <marijnfs!~marijnfs@D9797263.cm-3-2b.dynamic.ziggo.nl> has quit IRC (Ping timeout: 272 seconds)