{"action":"opened","issue":{"url":"https://api.github.com/repos/circuits/circuits/issues/131","labels_url":"https://api.github.com/repos/circuits/circuits/issues/131/labels{/name}","comments_url":"https://api.github.com/repos/circuits/circuits/issues/131/comments","events_url":"https://api.github.com/repos/circuits/circuits/issues/131/events","html_url":"https://github.com/circuits/circuits/issues/131","id":109286541,"number":131,"title":"WebSocketCodec should fire a connect","user":{"login":"mnlipp","id":1446020,"avatar_url":"https://avatars.githubusercontent.com/u/1446020?v=3","gravatar_id":"","url":"https://api.github.com/users/mnlipp","html_url":"https://github.com/mnlipp","followers_url":"https://api.github.com/users/mnlipp/followers","following_url":"https://api.github.com/users/mnlipp/following{/other_user}","gists_url":"https://api.github.com/users/mnlipp/gists{/gist_id}","starred_url":"https://api.github.com/users/mnlipp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mnlipp/subscriptions","organizations_url":"https://api.github.com/users/mnlipp/orgs","repos_url":"https://api.github.com/users/mnlipp/repos","events_url":"https://api.github.com/users/mnlipp/events{/privacy}","received_events_url":"https://api.github.com/users/mnlipp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-01T12:09:13Z","updated_at":"2015-10-01T12:09:13Z","closed_at":null,"body":"WebSocketCodec should fire a \"connect(self.\\_sock)\" event in its \\_\\_init\\_\\_ before it fires the first \"read\".\r\n\r\nWhile it is, of course, possible to deduce a new connection from the \"read\" events by checking for new sockets, it is quite tedious. And as we get a \"close\" event, it would only be reasonable and \"symmetrical\" to also get the corresponding \"connect\" event."}}