X-Git-Url: https://git.ucc.asn.au/?p=ipdf%2Fdocuments.git;a=blobdiff_plain;f=irc%2F%23ipdf.log;h=712aa0a2960811f321b98665575de42019b9c603;hp=25b73d1da310e920b43ca913c426f48d14090272;hb=fd35fa4f244a8c8494bac21957d6a682bdcfe842;hpb=05060637d0d1210d7a9c86ca09177888df303bcf

diff --git a/irc/#ipdf.log b/irc/#ipdf.log
index 25b73d1..712aa0a 100644
--- a/irc/#ipdf.log
+++ b/irc/#ipdf.log
@@ -2093,3 +2093,13 @@
 21:52 < matches> I figure if I implement everything in C++ it will be less "Webby"
 21:52 < matches> And more segfaultastic
 21:52  * sulix has a new favourite word.
+--- Day changed Thu Jun 26 2014
+14:58 < matches> I think the WebSocket RFC put this "Framing" business in just to confuse people
+14:58 < matches> My RFC Compliant* WebSocket server just sends the entire message in a single frame
+14:59 < matches> Doesn't TCP already do framing or something
+15:00 < matches> I mean, they specifically allow for frames with up to 2^63 bytes
+15:00 < matches> Sorry, bits not bytes
+15:02 < matches> So server -> client is pretty much TCP but you stick some stupid frame guff on the message
+15:02 < matches> client -> server involves... "masking"
+15:02 < matches> There are several long paragraphs on it
+15:10 < matches> I'm going to pretend this is related to precision