{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/Mvc/issues/3499","labels_url":"https://api.github.com/repos/aspnet/Mvc/issues/3499/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Mvc/issues/3499/comments","events_url":"https://api.github.com/repos/aspnet/Mvc/issues/3499/events","html_url":"https://github.com/aspnet/Mvc/issues/3499","id":115942338,"number":3499,"title":"Why is OAuthAuthorizationServerProvider coming with callbacks and virtuals?","user":{"login":"SetTrend","id":9283914,"avatar_url":"https://avatars.githubusercontent.com/u/9283914?v=3","gravatar_id":"","url":"https://api.github.com/users/SetTrend","html_url":"https://github.com/SetTrend","followers_url":"https://api.github.com/users/SetTrend/followers","following_url":"https://api.github.com/users/SetTrend/following{/other_user}","gists_url":"https://api.github.com/users/SetTrend/gists{/gist_id}","starred_url":"https://api.github.com/users/SetTrend/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SetTrend/subscriptions","organizations_url":"https://api.github.com/users/SetTrend/orgs","repos_url":"https://api.github.com/users/SetTrend/repos","events_url":"https://api.github.com/users/SetTrend/events{/privacy}","received_events_url":"https://api.github.com/users/SetTrend/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-09T19:02:32Z","updated_at":"2015-11-09T19:02:32Z","closed_at":null,"body":"I just had a look at the `OAuthAuthorizationServerProvider` class.\r\n\r\nIt comes with a bunch of `virtual` functions doing nothing but calling callback functions, stored in properties.\r\n\r\nThis implementation seems rather tautological to me: A derived class may decide whether to override the virtual functions or to overwrite the properties? Or even both?\r\n\r\nIs there a reason for this design decision? Otherwise I would suggest to decide for one dropping of them."}}