|
|
@ -34,6 +34,12 @@ This allows clients to load the previous messages on initial load.
|
|
34
|
34
|
|
|
35
|
35
|
* how do we websocket efficiently? should we batch (both client and
|
|
36
|
36
|
server), should/could we send binary?
|
|
|
37
|
* rooms. separate sockets or multiplex via one socket? then we'd need
|
|
|
38
|
some mechanism to list rooms, create them, optionally set a passphrase
|
|
|
39
|
or possibly other fancy things.
|
|
|
40
|
* names. and maybe other "properties". we could handle this using a
|
|
|
41
|
separate service that has mappings from the generated name to the
|
|
|
42
|
properties. clients could then decide to use that if they so desire.
|
|
37
|
43
|
|
|
38
|
44
|
## api playground
|
|
39
|
45
|
|