kore/examples/websocket
Joris Vink 7350131232 Allow listening of tls/notls ports at the same time.
Before kore needed to be built with NOTLS=1 to be able to do non TLS
connections. This has been like this for years.

It is time to allow non TLS listeners without having to rebuild Kore.

This commit changes your configuration format and will break existing
applications their config.

Configurations now get listener {} contexts:

listen default {
	bind 127.0.0.1 8888
}

The above will create a listener on 127.0.0.1, port 8888 that will serve
TLS (still the default).

If you want to turn off TLS on that listener, specify "tls no" in that
context.

Domains now need to be attached to a listener:

Eg:
	domain * {
		attach	default
	}

For the Python API this kills kore.bind(), and kore.bind_unix(). They are
replaced with:

	kore.listen("name", ip=None, port=None, path=None, tls=True).
2019-09-27 12:27:04 +02:00
..
assets Add websocket support to Kore. 2014-11-24 11:08:34 +01:00
conf Allow listening of tls/notls ports at the same time. 2019-09-27 12:27:04 +02:00
src initial fudging to add websockets to python 2017-01-29 22:57:34 +01:00
.gitignore Add websocket support to Kore. 2014-11-24 11:08:34 +01:00
README.md kore -> kodev where appropriate 2017-03-06 11:00:53 +01:00

README.md

Kore example websocket server

Run:

	# kodev run

Test:

	Open a browser that does websockets, surf to https://127.0.0.1:8888
	or whatever configured IP you have in the config.

	Hit the connect button to open a websocket session, open a second
	tab and surf to the same address and hit the connection button there
	as well. This should cause the number of messages sent/recv to keep
	incrementing as each message is broadcast to the other connection.