libwebsockets/minimal-examples/ws-server/minimal-ws-server-timer/mount-origin/index.html

<html>
 <head>
  <meta charset=utf-8 http-equiv="Content-Language" content="en"/>
  <script src="/example.js"></script>
 </head>
	<body>
		<img src="libwebsockets.org-logo.svg">
		<img src="strict-csp.svg"><br>

		LWS wsi timer <b>minimal ws server timer example</b>.<br>
		This opens a ws connection back to the server and just sits there
		setting the timer to fire every 20s, which resets the wsi timeout
		for 60s each timer.   It should just stay like that forever.
	</body>
</html>
sul: more paranoid casting vs libc header types As it is, if time_t is 32-bit on the platform it might lead to arithmetic overflow, so force it to lws_usec_t (uint64_t) even though it works OK here on x86_64. Add a minimal example aimed at testing the wsi hrtimer stability consistently across platforms. Add and disable by default hrtimer dump code (this is too expensive and specific to internal testing to leave in for debug mode even if it's not printed). If you hack it enabled, it will dump the sul list for the pt and assert if the list is disordered. 2019-10-27 06:17:35 +00:00			`<html>`
			`<head>`
			`<meta charset=utf-8 http-equiv="Content-Language" content="en"/>`
			`<script src="/example.js"></script>`
			`</head>`
			`<body>`
			`<img src="libwebsockets.org-logo.svg">`
			`<img src="strict-csp.svg"><br>`

			`LWS wsi timer <b>minimal ws server timer example</b>.<br>`
			`This opens a ws connection back to the server and just sits there`
			`setting the timer to fire every 20s, which resets the wsi timeout`
			`for 60s each timer. It should just stay like that forever.`
			`</body>`
			`</html>`