It needs some unixy environment that
may choke in other build contexts, this
lets you cleanly stop it being built
+
+--enable-x-google-mux Enable experimental x-google-mux support
+ in the build (see notes later in document)
Testing server with a browser
-----------------------------
by --protocol=protocolname
+Fraggle test app
+----------------
+
+By default it runs in server mode
+
+$ libwebsockets-test-fraggle
+libwebsockets test fraggle
+(C) Copyright 2010-2011 Andy Green <andy@warmcat.com> licensed under LGPL2.1
+ Compiled with SSL support, not using it
+ Listening on port 7681
+server sees client connect
+accepted v06 connection
+Spamming 360 random fragments
+Spamming session over, len = 371913. sum = 0x2D3C0AE
+Spamming 895 random fragments
+Spamming session over, len = 875970. sum = 0x6A74DA1
+...
+
+You need to run a second session in client mode, you have to
+give the -c switch and the server address at least:
+
+$ libwebsockets-test-fraggle -c localhost
+libwebsockets test fraggle
+(C) Copyright 2010-2011 Andy Green <andy@warmcat.com> licensed under LGPL2.1
+ Client mode
+Connecting to localhost:7681
+denied deflate-stream extension
+handshake OK for protocol fraggle-protocol
+client connects to server
+EOM received 371913 correctly from 360 fragments
+EOM received 875970 correctly from 895 fragments
+EOM received 247140 correctly from 258 fragments
+EOM received 695451 correctly from 692 fragments
+...
+
+The fraggle test sends a random number up to 1024 fragmented websocket frames
+each of a random size between 1 and 2001 bytes in a single message, then sends
+a checksum and starts sending a new randomly sized and fragmented message.
+
+The fraggle test client receives the same message fragments and computes the
+same checksum using websocket framing to see when the message has ended. It
+then accepts the server checksum message and compares that to its checksum.
+
+
proxy support
-------------
appear in the callback for protocol 0 and allow interface code to
manage socket descriptors in other poll loops.
-2011-02-12 Andy Green <andy@warmcat.com>
+
+x-google-mux support
+--------------------
+
+Experimental and super-preliminary x-google-mux support is available if
+enabled in ./configure with --enable-x-google-mux. Note that when changing
+configurations, you will need to do a make distclean before, then the new
+configure and then make ; make install. Don't forget the necessary other
+flags for your platform as described at the top of the readme.
+
+It has the following notes:
+
+ 1) To enable it, reconfigure with --enable-x-google-mux
+
+ 2) It conflicts with deflate-stream, use the -u switch on
+ the test client to disable deflate-stream
+
+ 3) It deviates from the google standard by sending full
+ headers in the addchannel subcommand rather than just
+ changed ones from original connect
+
+ 4) Quota is not implemented yet
+
+ 5) Close of subchannel is not really implemented yet
+
+ 6) Google opcode 0xf is changed to 0x7 to account for
+ v7 protocol changes to opcode layout
+
+ However despite those caveats, in fact it can run the
+ test client reliably over one socket (both dumb-increment
+ and lws-mirror-protocol), you can open a browser on the
+ same test server too and see the circles, etc.
+
+
+2011-05-23 Andy Green <andy@warmcat.com>