{"comment":{"created_at":"2011-10-18T10:36:49Z","body":"Ok, I've been wrong, processes are killed after timeout. The question is — why not to kill them after http client disconnect?","updated_at":"2011-10-18T10:36:49Z","url":"https://api.github.com/repos/nitrogen/nitrogen/issues/comments/2440205","id":2440205,"user":{"avatar_url":"https://secure.gravatar.com/avatar/37f16626f8d6312ccfa0036065e1884c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"37f16626f8d6312ccfa0036065e1884c","url":"https://api.github.com/users/si14","id":316910,"login":"si14"}},"action":"created","issue":{"number":37,"created_at":"2011-10-17T17:16:10Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"When user opens page with content like\r\n\r\n    body() ->\r\n        wf:comet(fun() -> counter(1) end),\r\n        #panel { id=p_container, body=[\r\n            #label { text=\"Messages so far:\" },\r\n            #panel { id=p_messages }\r\n        ]}.\r\n\r\ncounter/1 is spawned, but never killed if user didn't load .js files for some reason.\r\n","comments":3,"title":"Security flaw","updated_at":"2011-10-18T10:36:49Z","url":"https://api.github.com/repos/nitrogen/nitrogen/issues/37","id":1931077,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/37f16626f8d6312ccfa0036065e1884c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"37f16626f8d6312ccfa0036065e1884c","url":"https://api.github.com/users/si14","id":316910,"login":"si14"},"html_url":"https://github.com/nitrogen/nitrogen/issues/37","labels":[],"state":"open"},"legacy":{"issue_id":1931077,"comment_id":2440205}}