{"action":"opened","issue":{"url":"https://api.github.com/repos/zaphoyd/websocketpp/issues/566","repository_url":"https://api.github.com/repos/zaphoyd/websocketpp","labels_url":"https://api.github.com/repos/zaphoyd/websocketpp/issues/566/labels{/name}","comments_url":"https://api.github.com/repos/zaphoyd/websocketpp/issues/566/comments","events_url":"https://api.github.com/repos/zaphoyd/websocketpp/issues/566/events","html_url":"https://github.com/zaphoyd/websocketpp/issues/566","id":165500897,"number":566,"title":"Creating a Websocketpp-proxy, bidirectional communication.","user":{"login":"Paul-Ver","id":16624288,"avatar_url":"https://avatars.githubusercontent.com/u/16624288?v=3","gravatar_id":"","url":"https://api.github.com/users/Paul-Ver","html_url":"https://github.com/Paul-Ver","followers_url":"https://api.github.com/users/Paul-Ver/followers","following_url":"https://api.github.com/users/Paul-Ver/following{/other_user}","gists_url":"https://api.github.com/users/Paul-Ver/gists{/gist_id}","starred_url":"https://api.github.com/users/Paul-Ver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Paul-Ver/subscriptions","organizations_url":"https://api.github.com/users/Paul-Ver/orgs","repos_url":"https://api.github.com/users/Paul-Ver/repos","events_url":"https://api.github.com/users/Paul-Ver/events{/privacy}","received_events_url":"https://api.github.com/users/Paul-Ver/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-14T08:03:20Z","updated_at":"2016-07-14T08:03:20Z","closed_at":null,"body":"I'm creating a websocketpp-proxy that sets up a tunnel to another server, whenever a client connects to it.\r\n\r\nCurrently, I've merged the echo-server, utility-client and associative-storage examples.\r\nWhen a connection comes into the \"echo-server\"  it sets up a connection like in the utility client.\r\n\r\nLike this:\r\n\r\nClient--->[-> WSPP-server -> WSPP-endpoint ->]--->Server\r\n\r\nThis way I can forward the incoming messages to the external server.\r\nHowever, when a message comes back from the external server, it will be pushed into the message list.\r\n\r\nMy problems are:\r\n\r\n1. I can't send to the incoming connection from the connection_metadata::on_message.\r\nAnd/or\r\n2. I think I shouldn't continuously poll if messages have been received in one of the endpoints.\r\n\r\nSo my questions are:\r\n\r\n1. Is there any \"built-in\" support for tunnelling information between serving (incoming) and endpoint (outgoing) connections?\r\n2. In what way can I connect the incoming and outgoing connection, in a way that I can send messages from one to the other (bidirectional)?"}}
{"actor":{"display_login":"Paul-Ver"}}