| 08:32 | <benjamingr__> | annevk: did you end up filing a firefox bug for https://github.com/whatwg/dom/pull/919 ? (If not, should I?) |
| 15:31 | <croraf> | https://html.spec.whatwg.org/multipage/web-sockets.html says in the note "This interface does not allow for raw access to the underlying network. For example, this interface could not be used to implement an IRC client without proxying messages through a custom server." Why does an IRC client need the "raw access to the underlying network" and cannot be implemented using websockets? |
| 15:33 | <andreubotella> | websockets aren't TCP or UDP sockets |
| 15:33 | <andreubotella> | you can implement some version of IRC on top of websockets, but you can't connect to an IRC server using the IRC protocol with them |
| 15:37 | <croraf> | If you implement IRC on top of websockets why cannot you connect to the IRC server? |
| 15:38 | <andreubotella> | if you implement IRC on top of websockets, sure you can |
| 15:38 | <andreubotella> | but you won't be able to connect to freenode with websockets without setting up a proxy |
| 15:40 | <croraf> | Aha, I see, because you need to connect to the websockets server first, and freenode network does not provide that. |
| 15:42 | <andreubotella> | IRC is usually defined as a protocol that sits on top of TCP, and that's probably what the note meant |
| 15:43 | <andreubotella> | no reason why you can't port it to sit on top of websockets, I guess |
| 19:22 | <croraf> | I'm reading the html web-sockets spec https://html.spec.whatwg.org/multipage/web-sockets.html#dom-websocket-close . A note says that the messages enqueued with send will be sent prior to starting the Websocket closing handshake. But where can this be seen in the algorithm? |
| 19:30 | <croraf> | Also in https://html.spec.whatwg.org/multipage/web-sockets.html#dom-websocket-send it does not really specify what happens with the data that is sent when the websocket is in CLOSING. The bufferedAmount is still increased, but I don't see if this data is sent or not? |