Andy,

I will write a test client and server to match.

Actually, I think we should come up with a list of standardized sub-protocol
names that match to tests we can do for compatibility, and then also test
production servers don't accidentally deploy tests like echo.

I noticed you have a protocol name of  lws-mirror-protocol  for an echo
server.

How about:

org.ietf.websocket.test-echo              - echo all frames
org.ietf.websocket.test-echo-assemble     - echo messages after assembling
all fragments
org.ietf.websocket.test-echo-fragment     - echo frames randomly fragmented

org.ietf.websocket.test-consume           - consume all messages. Every 1s
send a text message formatted as follows "frames=%d messages=%d bytes=%d
binary=%d"
org.ietf.websocket.test-produce           - produce messages of random size
and fragmentation


It would be really handy if protocol names could be parameterised, so in the
last instance we could do something like:

org.ietf.websocket.
test-produce;minMsg=16;maxMsg=4096;fragment=true;pause=50ms

we could then also just have test-echo and the assemble and fragment
behaviours could be parameters.

cheers



On 8 March 2011 08:49, Andy Green <andy@warmcat.com> wrote:
> On 03/07/2011 05:48 PM, Somebody in the thread at some point said:
>>
>> I'm looking to test with a server that generates and sends fragmented
>> messages. Anyone implement that?
>
> libwebsockets supports fragmentation now, I added a fragmentation test
> server and client test applet to confirm it's at least internally
> consistent.  Greg I dunno if you're interested to knock something similar
up
> for Jetty like you did for the test ping applet?
>
> At the moment I had the test app turn off compression on the link.
>
> http://git.warmcat.com/cgi-bin/cgit/libwebsockets/
>
> Here's the README about it -->
>
> 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.
>
> -Andy
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>