Best Practices for Designing a Pragmatic RESTful API
Your data model has started to stabilize and you're in a position to create a public API for your web app. You realize it's hard to make significant changes to your API once it's released and want to get as much right as possible up front. Now, the internet has no shortage on opinions on API design. But, since there's no one widely adopted standard that works in all cases, you're left with a bunch
From REST to GraphQL
Disclaimer: GraphQL is still new and best practices are still emerging. This post describes some of my journey with implementing a GraphQL backend service, so it is a snapshot of what I’ve learned so far, presented in the hopes that it will be useful to others. Also, some of the specific real-world implementation details internal to Playlist have been paraphrased / simplified / anonymized for obvi
ãªãœ html ã® form 㯠PUT / DELETE をサãƒãƒ¼ãƒˆã—ãªã„ã®ã‹ï¼Ÿ
ãªã‚“㧠html ã® from 㯠PUT / DELETE ãŒã§ããªã„ã®ã‹ã€ã€Œã‚»ã‚ュリティ的ç†ç”±ã€ã¨ã‹ã€Œæ´å²çš„経緯ã€ã¨ã‹ã€ã‚ã‹ã£ãŸã‚ˆã†ãªåˆ†ã‹ã‚‰ãªã„よã†ãªèª¬æ˜Žã¯ã‚ˆãèžãã‘ã©ã€å®Ÿéš›ãªã‚“ã§ãªã®ã‹èª¿ã¹ã¦ãŸã‚‰è‰²ã€…æ•™ãˆã¦ã‚‚らã£ãŸè©±ã€‚ ã“ã“ã¾ã§ã‚ã‹ã£ãŸã“ã¨ã‚’ blog ã«ã¾ã¨ã‚ã¾ã—ãŸã€‚ / “ãªãœ html ã® form 㯠PUT / DELETE をサãƒãƒ¼ãƒˆã—ãªã„ã®ã‹ï¼Ÿ - Block Rockin’ Codes†http://jxck.hatenablog.com/entry/why-form-dosent-support-put-delete
RESTful Web アプリã®è¨è¨ˆãƒ¬ãƒ“ューã®è©±
1. RESTful Web アプリ㮠è¨è¨ˆãƒ¬ãƒ“ューã®è©± 和田 å“人 (a.k.a id:t-wada or @t_wada) July 23, 2012 @ sendagaya.rb 3. 自己紹介 åå‰: 和田 å“人 (ã‚ã ãŸãã¨) ブãƒã‚°: http://d.hatena.ne.jp/t-wada メール: takuto.wada@gmail.com Twitter: http://twitter.com/t_wada ã‚¿ãƒ¯ãƒ¼ã‚ºï½¥ã‚¯ã‚¨ã‚¹ãƒˆæ ªå¼ä¼šç¤¾ å–ç· å½¹ç¤¾é•· 4. ç§ã¨ REST (input) • WEB+DB PRESS vol.32「REST アーã‚テクãƒãƒ£ã‚¹ã‚¿ã‚¤ãƒ«å…¥é–€ã€ • ã¯ã¦ã¶è¨è¨ˆè°è«– • DHH ã® RubyKaigi 2006 Keynote • WEB+DB PRESS vol.38∼「REST レシピ〠• 『RESTful Web Serviceã€
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}