{"action":"created","issue":{"url":"https://api.github.com/repos/django/channels/issues/38","repository_url":"https://api.github.com/repos/django/channels","labels_url":"https://api.github.com/repos/django/channels/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/django/channels/issues/38/comments","events_url":"https://api.github.com/repos/django/channels/issues/38/events","html_url":"https://github.com/django/channels/issues/38","id":121853980,"node_id":"MDU6SXNzdWUxMjE4NTM5ODA=","number":38,"title":"Use WebRTC data channel instead of Websockets","user":{"login":"mitar","id":585279,"node_id":"MDQ6VXNlcjU4NTI3OQ==","avatar_url":"https://avatars3.githubusercontent.com/u/585279?v=4","gravatar_id":"","url":"https://api.github.com/users/mitar","html_url":"https://github.com/mitar","followers_url":"https://api.github.com/users/mitar/followers","following_url":"https://api.github.com/users/mitar/following{/other_user}","gists_url":"https://api.github.com/users/mitar/gists{/gist_id}","starred_url":"https://api.github.com/users/mitar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mitar/subscriptions","organizations_url":"https://api.github.com/users/mitar/orgs","repos_url":"https://api.github.com/users/mitar/repos","events_url":"https://api.github.com/users/mitar/events{/privacy}","received_events_url":"https://api.github.com/users/mitar/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2015-12-12T13:04:23Z","updated_at":"2018-08-20T14:56:14Z","closed_at":"2015-12-12T18:20:20Z","author_association":"NONE","body":"I think we should make a paradigm shift and move to use WebRTC instead of Websockets. This allows many interesting properties:\n- connections can be based on SCTP\n- have multi-path routing\n- you can have data packets which are reliable or unreliable\n- you can even have backpressure support (imagine that you could push back on Meteor publish because client cannot handle observes as quickly as server is pushing)\n\nThere is a great open source project already available which provides both client server suppor: https://github.com/feross/simple-peer\n\nSome interesting links to read:\n- https://github.com/webrtcftw/goals/issues/1\n- https://github.com/jbenet/random-ideas/issues/13\n"},"comment":{"url":"https://api.github.com/repos/django/channels/issues/comments/414345851","html_url":"https://github.com/django/channels/issues/38#issuecomment-414345851","issue_url":"https://api.github.com/repos/django/channels/issues/38","id":414345851,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNDM0NTg1MQ==","user":{"login":"caniko2","id":29519599,"node_id":"MDQ6VXNlcjI5NTE5NTk5","avatar_url":"https://avatars0.githubusercontent.com/u/29519599?v=4","gravatar_id":"","url":"https://api.github.com/users/caniko2","html_url":"https://github.com/caniko2","followers_url":"https://api.github.com/users/caniko2/followers","following_url":"https://api.github.com/users/caniko2/following{/other_user}","gists_url":"https://api.github.com/users/caniko2/gists{/gist_id}","starred_url":"https://api.github.com/users/caniko2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/caniko2/subscriptions","organizations_url":"https://api.github.com/users/caniko2/orgs","repos_url":"https://api.github.com/users/caniko2/repos","events_url":"https://api.github.com/users/caniko2/events{/privacy}","received_events_url":"https://api.github.com/users/caniko2/received_events","type":"User","site_admin":false},"created_at":"2018-08-20T14:56:14Z","updated_at":"2018-08-20T14:56:14Z","author_association":"NONE","body":"Do you know anything about aiortc? Can I use that along with django/django-channels to achieve what I need?"}}
{"actor":{"display_login":"caniko2"}}