{"action":"created","issue":{"url":"https://api.github.com/repos/yarpc/yarpc/issues/64","repository_url":"https://api.github.com/repos/yarpc/yarpc","labels_url":"https://api.github.com/repos/yarpc/yarpc/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/yarpc/yarpc/issues/64/comments","events_url":"https://api.github.com/repos/yarpc/yarpc/issues/64/events","html_url":"https://github.com/yarpc/yarpc/issues/64","id":163287786,"number":64,"title":"Explicit notion of Server on the RPC(plane)","user":{"login":"bombela","id":216204,"avatar_url":"https://avatars.githubusercontent.com/u/216204?v=3","gravatar_id":"","url":"https://api.github.com/users/bombela","html_url":"https://github.com/bombela","followers_url":"https://api.github.com/users/bombela/followers","following_url":"https://api.github.com/users/bombela/following{/other_user}","gists_url":"https://api.github.com/users/bombela/gists{/gist_id}","starred_url":"https://api.github.com/users/bombela/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bombela/subscriptions","organizations_url":"https://api.github.com/users/bombela/orgs","repos_url":"https://api.github.com/users/bombela/repos","events_url":"https://api.github.com/users/bombela/events{/privacy}","received_events_url":"https://api.github.com/users/bombela/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-06-30T23:20:26Z","updated_at":"2016-10-01T16:20:12Z","closed_at":"2016-10-01T16:20:12Z","body":"The yarpc library exposes a way to create a library context. Currently called \"RPC\". This context manages a set of inbound and outbound connections. The context accepts configuration of the different network transports.\r\n\r\nThis RPC context can instantiate many client channels. On the other hand, this RPC context can expose a single Server.\r\n\r\nInstead, let's have the ability to add as many Server as we want per RPC context. A server has a name, and a bunch of methods.\r\n\r\nExample: you have a service \"sawmill\" serving a bunch of logs. The service runs on a 100 machines. Each machine has a Go process with a single RPC context. This RPC context has a registered Server \"sawmill\". The sawmill server has a method \"get_logs\". The RPC context has also a second Server \"stats\", exposing process specific stats about this process.\r\n\r\nBecause a Server is now decoupled from the RPC context, it is possible to have reusable libraries of servers that can be attached to an RPC context at will.\r\n\r\nNote this is similar to the notion of namespacing. Although in this case we have a word and a concept to talk about and manipulate a bag of methods under the same umbrella."},"comment":{"url":"https://api.github.com/repos/yarpc/yarpc/issues/comments/250921194","html_url":"https://github.com/yarpc/yarpc/issues/64#issuecomment-250921194","issue_url":"https://api.github.com/repos/yarpc/yarpc/issues/64","id":250921194,"user":{"login":"breerly","id":263587,"avatar_url":"https://avatars.githubusercontent.com/u/263587?v=3","gravatar_id":"","url":"https://api.github.com/users/breerly","html_url":"https://github.com/breerly","followers_url":"https://api.github.com/users/breerly/followers","following_url":"https://api.github.com/users/breerly/following{/other_user}","gists_url":"https://api.github.com/users/breerly/gists{/gist_id}","starred_url":"https://api.github.com/users/breerly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/breerly/subscriptions","organizations_url":"https://api.github.com/users/breerly/orgs","repos_url":"https://api.github.com/users/breerly/repos","events_url":"https://api.github.com/users/breerly/events{/privacy}","received_events_url":"https://api.github.com/users/breerly/received_events","type":"User","site_admin":false},"created_at":"2016-10-01T16:20:12Z","updated_at":"2016-10-01T16:20:12Z","body":"This is solved by the Dispatcher concept now."}}
{"actor":{"display_login":"breerly"}}