{"title":"开发人员喜欢超媒体，但可能会抵制基于浏览器的OAuth授权","authors":"L. Richardson","doi":"10.1145/1798354.1798377","DOIUrl":null,"url":null,"abstract":"Although desktop developers often have trouble consciously understanding RESTful concepts like \"hypermedia as the engine of application state\", this does not prevent them from intuitively understanding client-side tools based on these concepts. However, I encountered unexpected developer resistance after implementing a security protocol I and other web developers had thought uncontroversial: the most common mechanism for authorizing OAuth request tokens.","PeriodicalId":268294,"journal":{"name":"International Workshop on RESTful Design","volume":"13 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2010-04-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Developers enjoy hypermedia, but may resist browser-based OAuth authorization\",\"authors\":\"L. Richardson\",\"doi\":\"10.1145/1798354.1798377\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Although desktop developers often have trouble consciously understanding RESTful concepts like \\\"hypermedia as the engine of application state\\\", this does not prevent them from intuitively understanding client-side tools based on these concepts. However, I encountered unexpected developer resistance after implementing a security protocol I and other web developers had thought uncontroversial: the most common mechanism for authorizing OAuth request tokens.\",\"PeriodicalId\":268294,\"journal\":{\"name\":\"International Workshop on RESTful Design\",\"volume\":\"13 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2010-04-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"International Workshop on RESTful Design\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1798354.1798377\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Workshop on RESTful Design","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1798354.1798377","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Developers enjoy hypermedia, but may resist browser-based OAuth authorization
Although desktop developers often have trouble consciously understanding RESTful concepts like "hypermedia as the engine of application state", this does not prevent them from intuitively understanding client-side tools based on these concepts. However, I encountered unexpected developer resistance after implementing a security protocol I and other web developers had thought uncontroversial: the most common mechanism for authorizing OAuth request tokens.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
