Newest at the top
2024-10-27 00:19:46 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
2024-10-27 00:15:27 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
2024-10-27 00:12:05 +0200 | euleritian | (~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer) |
2024-10-26 23:59:13 +0200 | hgolden__ | (~hgolden@169.150.203.23) (Ping timeout: 248 seconds) |
2024-10-26 23:56:49 +0200 | hgolden_ | (~hgolden@23.162.40.69) hgolden |
2024-10-26 23:55:48 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds) |
2024-10-26 23:54:52 +0200 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
2024-10-26 23:54:46 +0200 | <ash3en> | ok, will read more about this : ) |
2024-10-26 23:52:59 +0200 | <geekosaur> | which is typical for streaming audio protocols |
2024-10-26 23:52:27 +0200 | takuan | (~takuan@178-116-218-225.access.telenet.be) (Remote host closed the connection) |
2024-10-26 23:52:16 +0200 | <geekosaur> | most likely your coworker was talking about the OSC protocol doing an initial handshake and then streaming, which would be the same regardless of TCP/UDP/websockets |
2024-10-26 23:52:13 +0200 | <ash3en> | good night, at least where I am |
2024-10-26 23:52:03 +0200 | <ash3en> | I see, thank you very much! will think on this. got to go now but it won't be long until my next questions :D |
2024-10-26 23:51:30 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
2024-10-26 23:51:13 +0200 | <geekosaur> | the whole point of websockets being that you don't have permission to use system sockets and often don't have permission to do anything more than different endpoints on port 443 |
2024-10-26 23:50:29 +0200 | <geekosaur> | (it may be a multiplexer handshake instead, I'm a little weak on websockets, I mostly work with system sockets) |
2024-10-26 23:50:07 +0200 | <geekosaur> | right, but TCP only requires one at the beginning as well. that, however, is still protocol aside from the TCP 3-way handshake, which will still be there in some sense |
2024-10-26 23:49:09 +0200 | <ash3en> | complex |
2024-10-26 23:49:03 +0200 | <ash3en> | geekosaur: it is! |
2024-10-26 23:48:54 +0200 | <ash3en> | The info I got was, that Websockets pass the responsibility of ack to lower levels and there is only a -- maybe it was a handshake, would that change something? -- on start instead of all the time |
2024-10-26 23:48:11 +0200 | <geekosaur> | networking is complex 🙂 |
2024-10-26 23:47:44 +0200 | <geekosaur> | slightly slower, since you would have OSC protocol overhead and browser websocket protocol over HTTPS overhead |
2024-10-26 23:47:10 +0200 | <ash3en> | so after all it would be as fast as "usual" OSC over TCP? |
2024-10-26 23:44:50 +0200 | <geekosaur> | (TCP ACKs are more complicated than "one per message" except on theoretically perfect one-to-one networks, and sometimes even then) |
2024-10-26 23:43:56 +0200 | <geekosaur> | even websockets uses one-per-message (sort of), but you need a raw system socket to observe it |
2024-10-26 23:42:54 +0200 | <geekosaur> | it's a protocol thing, not a socket implementation thing |
2024-10-26 23:42:22 +0200 | <ash3en> | sounded like websockets to me |
2024-10-26 23:42:00 +0200 | <ash3en> | it was something about how just an initial acknowledge is used vs one for every msg |
2024-10-26 23:41:08 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
2024-10-26 23:40:27 +0200 | <ash3en> | I wonder if it's a thing even.. maybe I misunderstood my colleague |
2024-10-26 23:40:15 +0200 | pavonia | (~user@user/siracusa) siracusa |
2024-10-26 23:37:45 +0200 | <geekosaur> | I see no websoket support in there |
2024-10-26 23:37:33 +0200 | <geekosaur> | yeh, just traced through the implementation, it's system sockets |
2024-10-26 23:35:57 +0200 | <ash3en> | thanks |
2024-10-26 23:33:20 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
2024-10-26 23:32:11 +0200 | <geekosaur> | no, it's system sockets, not websockets |
2024-10-26 23:31:35 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
2024-10-26 23:30:59 +0200 | petrichor | (~znc-user@user/petrichor) (Ping timeout: 252 seconds) |
2024-10-26 23:27:36 +0200 | <ash3en> | is this for OSC use with websockets? https://github.com/rd--/hosc/blob/master/Sound/Osc/Transport/Fd/Socket.hs |
2024-10-26 23:22:18 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
2024-10-26 23:15:36 +0200 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 252 seconds) |
2024-10-26 23:15:20 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
2024-10-26 23:11:22 +0200 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) |
2024-10-26 23:09:52 +0200 | ljdarj1 | ljdarj |
2024-10-26 23:09:52 +0200 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds) |
2024-10-26 23:08:32 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
2024-10-26 23:06:26 +0200 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
2024-10-26 23:04:46 +0200 | AlexZenon | (~alzenon@178.34.161.119) |
2024-10-26 23:04:33 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
2024-10-26 23:02:15 +0200 | AlexZenon | (~alzenon@178.34.161.119) (Ping timeout: 246 seconds) |