{"action":"created","issue":{"url":"https://api.github.com/repos/peers/peerjs-server/issues/98","repository_url":"https://api.github.com/repos/peers/peerjs-server","labels_url":"https://api.github.com/repos/peers/peerjs-server/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/peers/peerjs-server/issues/98/comments","events_url":"https://api.github.com/repos/peers/peerjs-server/issues/98/events","html_url":"https://github.com/peers/peerjs-server/issues/98","id":223110008,"number":98,"title":"How to peer discover without using socket.io","user":{"login":"macdasi","id":6370865,"avatar_url":"https://avatars3.githubusercontent.com/u/6370865?v=3","gravatar_id":"","url":"https://api.github.com/users/macdasi","html_url":"https://github.com/macdasi","followers_url":"https://api.github.com/users/macdasi/followers","following_url":"https://api.github.com/users/macdasi/following{/other_user}","gists_url":"https://api.github.com/users/macdasi/gists{/gist_id}","starred_url":"https://api.github.com/users/macdasi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/macdasi/subscriptions","organizations_url":"https://api.github.com/users/macdasi/orgs","repos_url":"https://api.github.com/users/macdasi/repos","events_url":"https://api.github.com/users/macdasi/events{/privacy}","received_events_url":"https://api.github.com/users/macdasi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-04-20T15:37:42Z","updated_at":"2017-04-26T09:06:46Z","closed_at":null,"body":"Is there a way to let know other peers (A) when a peer (B) is connected / disconnected ? \r\nWith regard to : \r\nA don't know B peerid .\r\nI don't want to use another websocket like socket.io \r\nI think ExpressPeerServer has members that control socket to peers , so all I got to do is iterate each one and emit a message ... I can't find a way to do it . \r\nI don't want the client to make xhr request for peers list or use peer.listAllPeers()  "},"comment":{"url":"https://api.github.com/repos/peers/peerjs-server/issues/comments/297308014","html_url":"https://github.com/peers/peerjs-server/issues/98#issuecomment-297308014","issue_url":"https://api.github.com/repos/peers/peerjs-server/issues/98","id":297308014,"user":{"login":"luongnv89","id":3288457,"avatar_url":"https://avatars1.githubusercontent.com/u/3288457?v=3","gravatar_id":"","url":"https://api.github.com/users/luongnv89","html_url":"https://github.com/luongnv89","followers_url":"https://api.github.com/users/luongnv89/followers","following_url":"https://api.github.com/users/luongnv89/following{/other_user}","gists_url":"https://api.github.com/users/luongnv89/gists{/gist_id}","starred_url":"https://api.github.com/users/luongnv89/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/luongnv89/subscriptions","organizations_url":"https://api.github.com/users/luongnv89/orgs","repos_url":"https://api.github.com/users/luongnv89/repos","events_url":"https://api.github.com/users/luongnv89/events{/privacy}","received_events_url":"https://api.github.com/users/luongnv89/received_events","type":"User","site_admin":false},"created_at":"2017-04-26T09:06:46Z","updated_at":"2017-04-26T09:06:46Z","body":"@macdasi You can create a virtual peer which will work like a NETWORK OPERATOR (OP - has a fixed ID). So every peer will first connect with OP, then OP will provide the information of other peers (like list of peer ids), then the new peer can connect with another peer (it also can keep connect with OP if you want).\r\nI have not implemented this idea yet, just a pop idea in my head."}}
{"actor":{"display_login":"luongnv89"}}