{"action":"created","issue":{"url":"https://api.github.com/repos/iiag/iiag/issues/1","labels_url":"https://api.github.com/repos/iiag/iiag/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/iiag/iiag/issues/1/comments","events_url":"https://api.github.com/repos/iiag/iiag/issues/1/events","html_url":"https://github.com/iiag/iiag/issues/1","id":66498340,"number":1,"title":"Communication protocol","user":{"login":"sjrct","id":1354804,"avatar_url":"https://avatars.githubusercontent.com/u/1354804?v=3","gravatar_id":"","url":"https://api.github.com/users/sjrct","html_url":"https://github.com/sjrct","followers_url":"https://api.github.com/users/sjrct/followers","following_url":"https://api.github.com/users/sjrct/following{/other_user}","gists_url":"https://api.github.com/users/sjrct/gists{/gist_id}","starred_url":"https://api.github.com/users/sjrct/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sjrct/subscriptions","organizations_url":"https://api.github.com/users/sjrct/orgs","repos_url":"https://api.github.com/users/sjrct/repos","events_url":"https://api.github.com/users/sjrct/events{/privacy}","received_events_url":"https://api.github.com/users/sjrct/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/iiag/iiag/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/iiag/iiag/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-04-06T00:39:21Z","updated_at":"2015-04-10T03:47:50Z","closed_at":null,"body":"Reflective of issue [#43](https://github.com/iiag/iiag-legacy/issues/43) in iiag-legacy. We need a communication protocol between the server and the client.\r\n\r\nPerhaps event based? So when an event happens that the client can see, an event message is sent to the client, and they can update accordingly. Perhaps there should be a method for the client to query for other information as well, though I think the events should in theory provide sufficient information provided the client and server do not go out of sync."},"comment":{"url":"https://api.github.com/repos/iiag/iiag/issues/comments/91419611","html_url":"https://github.com/iiag/iiag/issues/1#issuecomment-91419611","issue_url":"https://api.github.com/repos/iiag/iiag/issues/1","id":91419611,"user":{"login":"Grissess","id":1500742,"avatar_url":"https://avatars.githubusercontent.com/u/1500742?v=3","gravatar_id":"","url":"https://api.github.com/users/Grissess","html_url":"https://github.com/Grissess","followers_url":"https://api.github.com/users/Grissess/followers","following_url":"https://api.github.com/users/Grissess/following{/other_user}","gists_url":"https://api.github.com/users/Grissess/gists{/gist_id}","starred_url":"https://api.github.com/users/Grissess/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Grissess/subscriptions","organizations_url":"https://api.github.com/users/Grissess/orgs","repos_url":"https://api.github.com/users/Grissess/repos","events_url":"https://api.github.com/users/Grissess/events{/privacy}","received_events_url":"https://api.github.com/users/Grissess/received_events","type":"User","site_admin":false},"created_at":"2015-04-10T03:47:50Z","updated_at":"2015-04-10T03:47:50Z","body":"AFAIK Berkeley sockets *are* rather portable (cf. WinSock). The problem may be that they're too cumbersome or low-level :P. \r\n\r\nFrankly, though, I'm most comfortable at that level--with some Python niceties, of course."}}