{"issue":{"created_at":"2011-11-24T07:58:34Z","state":"closed","updated_at":"2011-12-07T20:41:25Z","user":{"gravatar_id":"32749918297d65da5eafbaa64d95a4b8","id":1138805,"url":"https://api.github.com/users/ShyRed","login":"ShyRed","avatar_url":"https://secure.gravatar.com/avatar/32749918297d65da5eafbaa64d95a4b8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":1,"body":"The server side ```UserContext``` Connect delegate does not behave like one might expect...\r\n\r\n**What I expect:**\r\nThe Connect delegate is called once the connection establishing and handshake are complete, so I can greet every newly connected user with a \"welcome message\" inside the Connect delegate.\r\n\r\n**What happens:**\r\nThe Connect delegate is called before the handshake which causes errors / disconnects, if one messages the client inside the Connect delegate.\r\n\r\n**Workaround:**\r\nRight now you have to poll the ```UserContext.IsSetup``` property in order to find out when a client is ready for receiving custom messages.\r\n\r\n**Solution:**\r\n1) Call the Connect delegate after the handshake.\r\n*OR*\r\n2) Split the delegate into 2 separate delegates: Connecting (is called before handshake) and Connected (is called after handshake).\r\n\r\n","assignee":{"gravatar_id":"3934113e22dd0a3d31fe1c8aab8e0d8f","id":116584,"url":"https://api.github.com/users/Kythera","login":"Kythera","avatar_url":"https://secure.gravatar.com/avatar/3934113e22dd0a3d31fe1c8aab8e0d8f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"number":11,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"id":2338299,"labels":[],"title":"UserSocket Connect not behaving like expected","html_url":"https://github.com/Olivine-Labs/Alchemy-Websockets/issues/11","closed_at":"2011-12-07T20:41:25Z","url":"https://api.github.com/repos/Olivine-Labs/Alchemy-Websockets/issues/11","milestone":null},"action":"closed"}