kore/examples/pipe_task
Joris Vink e98a4ddab5 Change how routes are configured in Kore.
Routes are now configured in a context per route:

route /path {
	handler handler_name
	methods get post head
	validate qs:get id v_id
}

All route related configurations are per-route, allowing multiple
routes for the same path (for different methods).

The param context is removed and merged into the route context now
so that you use the validate keyword to specify what needs validating.
2021-09-15 11:09:52 +02:00
..
assets Add user callbacks for task activity. 2015-07-01 11:01:23 +02:00
conf Change how routes are configured in Kore. 2021-09-15 11:09:52 +02:00
src Change how routes are configured in Kore. 2021-09-15 11:09:52 +02:00
.gitignore Add user callbacks for task activity. 2015-07-01 11:01:23 +02:00
README.md kore -> kodev where appropriate 2017-03-06 11:00:53 +01:00

README.md

Kore example of tasks and websockets.

This example connects Kore via task to a named unix pipe and spews out any output to all connected websocket clients.

Before you run this make the pipe: $ mkfifo /tmp/pipe

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.

	Now connect a writer endpoint to the named pipe (/tmp/pipe):
		$ echo "hello" > /tmp/pipe

	You should see the result in your browser.