Switch to DuckDuckGo Search
   January 13, 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 | >

Toggle Join/Part | bottom
[00:10:30] *** imMute <imMute!~immute@45.56.78.57> has joined #zeromq
[00:10:30] *** imMute <imMute!~immute@45.56.78.57> has quit IRC (Changing host)
[00:10:30] *** imMute <imMute!~immute@about/networking/240.255.255.0/imMute> has joined #zeromq
[00:26:09] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has quit IRC (Quit: krychu)
[00:40:16] <Flash> haasn: 'bind' in ZMQ is only tangentially related to 'bind' in BSD sockets. Yes exactly one person must bind to the address, but it doesn't matter which side does it
[00:40:48] <Flash> so multiple receivers can absolutely listen to the same socket; they just need to connect() not bind()
[00:41:28] <haasn> I have a long-running process (with a daemon flavor) and a short-running process that controls the long-running process via IPC
[00:41:50] <haasn> The long-running process only needs to receive "control events". There are no replies
[00:42:16] <Flash> point being, your long-running process would typically be the one to bind()
[00:42:23] <haasn> So technically, I can't have the "controller" bind, because the long-running process wouldn't know when to connect
[00:42:52] <haasn> Yes I agree, the only thing that makes sense here is to have the long-running process (receiver) bind and the short-running process (sender) connect
[00:43:03] <Flash> yep. that's the philosophy
[00:43:11] <haasn> I was just thinking along the lines of: could I make multiple long-running processes listen on the same path somehow
[00:43:24] <haasn> so that I can "broadcast" the control event to multiple daemons at once
[00:43:48] <haasn> but it seems this would not be possible without some sort of middle-man / router /whatnot
[00:43:58] <Flash> yes, but only one can bind. Note that the guide suggests that you are moving to a more complex model where you have a single federator handle the bind and pass traffic to whomever
[00:44:11] <Flash> correct; that is the use case for a router
[00:44:45] <Flash> as a sanity check, you couldn't do it with TCP sockets either, without some middle-man
[00:45:39] <haasn> Right, but it would be possible with some flavor of UDP multi/broadcast, right?
[00:45:50] <Flash> yes
[00:46:09] <Flash> but UDP is not guaranteed to be reliable
[00:46:12] <haasn> hence why I was wondering if ZMQ under UDP would allow you to do things like this
[00:46:46] <Flash> seems like you are circling around conflicting requirements
[00:47:00] <haasn> oh, my problem is solved
[00:47:03] <Flash> you don't want to lose messages, so UDP is not possible
[00:47:05] <haasn> I'm mostly just curious now
[00:48:55] <haasn> Tangentially, I wonder under what scenarios UDP is unreliable on localhost. I guess the kernel will drop UDP packets if the receiving end hasn't been draining its buffers?
[02:39:20] *** nyexpress <nyexpress!~textual@unaffiliated/nyexpress> has joined #zeromq
[03:10:39] *** nyexpress <nyexpress!~textual@unaffiliated/nyexpress> has quit IRC (Quit: nyexpress)
[07:06:27] *** aleph- <aleph-!~hatter@lobsters/Auditor/Church-> has quit IRC (Ping timeout: 268 seconds)
[11:23:07] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has joined #zeromq
[11:42:55] *** drbobbeaty <drbobbeaty!~drbob@2601:249:1000:71d0:a894:3f3f:2c7e:abea> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
[11:46:24] *** drbobbeaty <drbobbeaty!~drbob@2601:249:1000:71d0:b0ab:9a20:f5cc:e150> has joined #zeromq
[17:11:22] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has quit IRC (Quit: krychu)
[17:14:20] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has joined #zeromq
[17:47:01] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has quit IRC (Quit: krychu)
[17:47:38] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has joined #zeromq
[18:01:03] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has quit IRC (Quit: krychu)
[18:02:11] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has joined #zeromq
[18:13:06] *** krychu <krychu!~krychu@2a02:1205:505c:2ab0:71ee:ce21:724d:7a0d> has quit IRC (Quit: krychu)
[19:04:33] *** aleph- <aleph-!~hatter@lobsters/Auditor/Church-> has joined #zeromq
[20:38:43] *** guido_g <guido_g!~guido_g@31.16.116.251> has quit IRC (Quit: Leaving.)
[21:04:58] *** aleph- <aleph-!~hatter@lobsters/Auditor/Church-> has quit IRC (Ping timeout: 272 seconds)
[21:26:16] *** aleph- <aleph-!~hatter@lobsters/Auditor/Church-> has joined #zeromq
top

   January 13, 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 | >