リソースã®ä¸€éƒ¨æ›´æ–°ã«ãŠã‘ã‚‹URLè¨è¨ˆ - Qiita
Deleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article? æ¦‚è¦ Webアプリケーションã«ã¦ã€ãƒªã‚½ãƒ¼ã‚¹ã®ä¸€éƒ¨æ›´æ–°ã‚’è¡Œã†éš›ã€ã©ã®ã‚ˆã†ã«URLè¨è¨ˆã‚’è¡Œã†ã¨ã‚·ãƒ³ãƒ—ルã§ç¾Žã—ã„ã‹ï¼ˆæœ¬å½“ã¯ãã“ã¾ã§è€ƒãˆã¦ã„ãªã‹ã£ãŸã‘ã©ï¼‰æ‚©ã‚“ã§ã„ãŸã¨ã“ã‚〠@t_wada ã•ã‚“ã‹ã‚‰ç´ 敵ãªè¨è¨ˆæŒ‡é‡ã‚’ã”教示ã„ãŸã ãã¾ã—ãŸã€‚ 本記事ã¯ãã®å†…容ã«åŠ ãˆã¦ã€å®Ÿéš›ã«è‡ªåˆ†ã§è¡Œã£ãŸã“ã¨ã€èª¿ã¹ãŸã“ã¨ã€æ€ã£ãŸäº‹ãªã©ã€ã¾ã¨ã‚ã¦ãŠã‚Šã¾ã™ã€‚ ã‚らã™ã˜ 数週間å‰ã«SIピラミッドã‹ã‚‰ãƒ’モãªã—ãƒãƒ³ã‚¸ãƒ¼ã‚’決ã‚ã¦Webã®ä¸–ç•Œã«é£›ã³è¾¼ã‚“ã ç§ã¯ã€å°ã•ãªå°ã•ãªWebアプリケーションをrails newã‹ã‚‰æ‰‹æŽ¢ã‚Šã§ä½œã£ã¦ã„ã¾ã—ãŸã€‚ ãã‚“ãªã¨ãã€ç°¡å˜ãªãƒªã‚½ãƒ¼ã‚¹ã®ä¸€éƒ¨æ›´æ–°æ©Ÿèƒ½
REST API Design - Resource Modeling
“The key abstraction of information in REST is a resource. Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on. In other words, any concept that might be the target of an author's hypertext reference must fit within the definition of a r
RESTful#ã¨ã¯å‹‰å¼·ä¼š9
èªæ›¸ä¼šã«é–¢ã—㦠グループã§å£°ã«å‡ºã—ã¦è¼ªèªã—ã€ç–‘å•ç‚¹ãªã©ã‚’出ã—ã¤ã¤ã€å·æ‘ã•ã‚“ã«è³ªå•ã™ã‚‹ã¨ã„ã†å½¢å¼ã§è¡Œã£ã¦ã„ã¾ã™ ã“ã‚Œã¾ã§6回開催ã—ã€3ã€5ã€6ã€7ã€8ã€9ç« ã‚’æŠœç²‹ã—ã¦èªã¿ã¾ã—ãŸã€‚ 「#RESTudyã€ã§æ¤œç´¢ã™ã‚‹ã¨ã€è©±ã—åˆã‚ã‚ŒãŸå†…容ç‰ãŒã‚ã‹ã‚‹ã¨æ€ã„ã¾ã™ã€‚ 今回ã¯ä»¥ä¸‹ã®ãƒšãƒ¼ã‚¸ã‹ã‚‰ã‚„ã‚Šã¾ã™ã®ã§ã€å½“æ—¥ã¾ã§ã«ç›®ã‚’通ã—ã¦ã„ãŸã ãã¨è‰¯ã„ã§ã™ã€‚ 「P132 9.6 コンテントãƒã‚´ã‚·ã‚¨ãƒ¼ã‚·ãƒ§ãƒ³ã€ ä¼šå ´ã«ã¤ã„㦠è¨å‚™ Wifiã‚ã‚Šã¾ã™ 飲食ã§ãã¾ã™ 但ã—ã€ã‚´ãƒŸã¯æŒã¡å¸°ã£ã¦ãã ã•ã„ ç¦ç…™ã§ã™ 20時ã¾ã§ã«æ¥å ´ã•ã‚Œã‚‹å ´åˆ ビルã®æ£é¢çŽ„é–¢(サンクスã®å·¦æ‰‹)ã‹ã‚‰ã‚¨ãƒ¬ãƒ™ãƒ¼ã‚¿ãƒ¼ã«ä¹—ã‚Šã€7階ã¾ã§ãŠè¶Šã—下ã•ã„。 20時以é™ã«æ¥å ´ã•ã‚Œã‚‹å ´åˆ æ£é¢çŽ„é–¢ã‹ã‚‰è¦‹ã¦å³å´ã«é€šç”¨å£ãŒã‚ã‚Šã¾ã™ã€‚ ãã“ã«ã‚るインターフォン㧠702 を鳴らã—ã¦ãã ã•ã„。 é–‹éŒ ã•ã‚Œã¾ã—ãŸã‚‰é€šç”¨å£ã‹ã‚‰å…¥ã‚Šã€ã‚¨ãƒ¬ãƒ™ãƒ¼ã‚¿ãƒ¼ã«ä¹—ã£ã¦7階ã®ä¼šå ´ã¾ã§ãŠè¶Šã—ãã ã•ã„。 ※ 2
Rubyist Magazine - スã¯ã‚¹ãƒšãƒƒã‚¯ã®ã‚¹ ã€ç¬¬ 1 回】 RSpec ã®æ¦‚è¦ã¨ã€RSpec on Rails (モデル編)
『るã³ã¾ã€ã¯ã€Ruby ã«é–¢ã™ã‚‹æŠ€è¡“記事ã¯ã‚‚ã¡ã‚ã‚“ã®ã“ã¨ã€Rubyist ã¸ã®ã‚¤ãƒ³ã‚¿ãƒ“ューやエッセイã€ãã®ä»–ã‚’ãŠå±Šã‘ã™ã‚‹ã‚¦ã‚§ãƒ–雑誌ã§ã™ã€‚ Rubyist Magazine ã«ã¤ã„㦠『Rubyist Magazineã€ã€ç•¥ã—ã¦ã€Žã‚‹ã³ã¾ã€ã¯ã€Rubyist ã® Rubyist ã«ã‚ˆã‚‹ã€Rubyist ã¨ãã†ã§ãªã„人ã®ãŸã‚ã®ã‚¦ã‚§ãƒ–雑誌ã§ã™ã€‚ æœ€æ–°å· Rubyist Magazine 0064 å· ãƒãƒƒã‚¯ãƒŠãƒ³ãƒãƒ¼ Rubyist Magazine 0064 å· Rubyist Magazine 0063 å· Rubyist Magazine 0062 å· Kaigi on Rails ç‰¹é›†å· RubyKaigi Takeout 2020 ç‰¹é›†å· Rubyist Magazine 0061 å· Rubyist Magazine 0060 å· RubyKaigi 2019 ç›´å‰ç‰¹é›†å· Rubyist
JSON Hyper-Schemaã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スディスクリプションãŒã†ã¾ãã„ã‹ãªã„ç†ç”± - ã¶ã‚ã。@ã¯ã¦ãª
RubyKaigiã®ç™ºè¡¨ã®ãŸã‚ã«è€ƒãˆã¦ã„ãŸã®ã§ã™ãŒã€ç™ºè¡¨æœ¬ç·¨ã«è©³ã—ã入れられãªããªã‚Šãã†ãªã®ã§ã€ã¾ã¨ã¾ã‚Šãªã„ã§ã™ãŒãƒ–ãƒã‚°ã«æ›¸ã„ã¦ã¿ã¾ã™ã€‚ SOAPã§ã„ã†WSDL(Web Service Definition Language)ã®ã‚ˆã†ãªã€ã‚µãƒ¼ãƒ“スã®ã‚¤ãƒ³ã‚¿ãƒ•ã‚§ãƒ¼ã‚¹ã‚’定義・記述ã™ã‚‹ãŸã‚ã®ã—ãã¿ã‚’ç·ç§°ã—ã¦IDL(Interface Description Language)ã¨å‘¼ã³ã¾ã™ã€‚ JSON Hyper-Schema*1ã‚‚IDLã€ã‚µãƒ¼ãƒ“スディスクリプションã®ä¸€ç¨®ã¨ã„ãˆã¾ã™ã€‚ Webã®IDLã¯ä»Šã¾ã§ã«ã‚‚ãŸãã•ã‚“出ã¦ãã¦ã€ã—ã‹ã—ã†ã¾ãã„ã£ã¦ã„ã¾ã›ã‚“。 ãªãœã§ã—ょã†ï¼Ÿ @yohei ã•ã‚“æ›°ã〠RESTã¯çµ±ä¸€ã‚¤ãƒ³ã‚¿ãƒ•ã‚§ãƒ¼ã‚¹ãªã‚“ã ã‹ã‚‰ã€ãã“ã«ã•ã‚‰ã«ã‚¤ãƒ³ã‚¿ãƒ•ã‚§ãƒ¼ã‚¹ã‚’定義ã™ã‚‹ã®ã¯ãŠã‹ã—ㄠ（API Meetup #1 質疑応ç”より） WebAPIã®ã“ã‚Œã¾ã§ã¨ã“ã‚Œã‹ã‚‰ from yohei ã“ã‚Œã¯ã©ã†ã„ã†ã“
#mozaicfm REST ã‚’è´ã„ã¦ã®æ„Ÿæƒ³ - ã¶ã‚ã。@ã¯ã¦ãª
mozaic.fmã§RESTã®å›žãŒä¼ç”»ã•ã‚Œã¦ã„ã‚‹ã¨ã„ã†ã“ã¨ã‚’ã€API Meetup #1 ã®ã¨ãã« yohei ã•ã‚“ã‹ã‚‰ç›´æŽ¥èžã„ã¦ã„ãŸã®ã§ã™ãŒã€ã¤ã„ã«ãã‚ŒãŒå…¬é–‹ã•ã‚ŒãŸã®ã§ã€å–œã³å‹‡ã‚“ã§è´ãã¾ã—ãŸã€‚ mozaic.fm #7 REST æ–片的ã«æ„Ÿæƒ³ã‚’ツイートã—ãŸã®ã§ã€ãã®ã¾ã¨ã‚ã§ã™ã€‚ RESTã®ä½•ãŒé‡è¦ãªã®ã‹ ã•ã™ãŒã® t_wada ã•ã‚“。アーã‚テクãƒãƒ£ã¨ã—ã¦ã‚‚ãã†ã ã—ã€ã‚¢ãƒ—リケーションフレームワークも「é©åˆ‡ãªåˆ¶ç´„ã€ã‚’è¨ã‘ã‚‹ã“ã¨ã§è¨è¨ˆã®ã‚³ã‚¹ãƒˆãŒä¸‹ãŒã‚‹ã€ã¨ã„ã†è©±ã®æµã‚Œã§ã—ãŸã€‚ “Constraints are liberatingâ€ã€Œåˆ¶ç´„ã¯è‡ªç”±ã‚’ã‚‚ãŸã‚‰ã™ã€ã¯åƒ•ãŒå¥½ããªè¨€è‘‰ã§ã™ãŒã€ã“れを知ã£ãŸã®ã¯DHHã®RubyKaigi 2006ã®è¬›æ¼”ã‹ã‚‰ã§ã™ã€‚（åˆå‡ºã¯ã©ã“ã‹åˆ¥ã®ã¨ã“ã‚ãªã®ã‹ã‚‚？） RESTã®æµè¡Œ 原ç†ä¸»ç¾©è€…的発言をã™ã‚‹ãªã‚‰ã€ã€ŒREST APIã€ã¨è¬³ã£ã¦ä¸–ã«å‡ºãŸWeb APIã¯ãŸã ã®JSON/X
REST: From GET to HATEOAS
Presentation I gave at JPoint Meetingpoint (in a slight different version) and GotoCon Amsterdam 2012. How to get your API or service from using the basic REST principles such as verbs and resources to a complete RESTful service that fully supports "Hypermedia as the engine of application state" (HATEOAS). More info at www.smartjava.orgRead less
APIã®ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã¯é™å±€åˆ†å²ã§ã‚„ã‚‹ã®ãŒè‰¯ã„ - Hidden in Plain Sight
ã¡ã‚‡ã£ã¨å‰ã«Twitterã§APIã®ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’ã©ã†ã‚„ã‚‹ã‹ã¿ãŸã„ãªè©±ã‚’ã—ã¦ã„ãŸã®ã§ã™ãŒã€ãã®ã¸ã‚“ã‚‚ã‚„ã‚‚ã‚„ã—ã¦ã„ã‚‹ã®ã§å°‘ã—æ•´ç†ã—ã¦ãŠããŸã„ãªã¨ã€‚ APIã®URLã‚’/api/v1/*ã¨ã‹ã£ã¦ã‚„ã‚‹ã®ã€ã‚„ã‚ãŸã»ã†ãŒã„ã„ã¨ãŠã‚‚ã†ã‚“ã ã‘ã©ãªã。ã„ã–v2を作るã¨ãªã£ãŸã¨ãã«ã€å¤§é‡ã®ã‚³ãƒ”ペãŒç™ºç”Ÿã—ã¦å¾Œæ‚”ã™ã‚‹ã‚ˆã€ã£ã¦ä¼ãˆãŸã„。— Kenn Ejima (@kenn) February 28, 2014 ã•ã¦ã€ã“ã‚Œã«ã¤ã„ã¦è‰²ã€…ã¨ç•°è«–・åè«–ã‚‚å«ã‚ãŸæ„見ãŒå‡ºãŸã®ã§ã™ãŒã€ã¾ãšã¯ã€å¤§æ˜”ã«URLæ–¹å¼ï¼ˆï¼ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©åˆ†å‰²ï¼‰ã§ã‚„ã£ã¦ãã¦å¾Œæ‚”ã—ãŸã¼ããŒã€ï¼ˆ5å¹´ãらã„å‰ã‹ã‚‰ï¼‰ç¾åœ¨ã¯ã©ã†ã‚„ã£ã¦APIã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’管ç†ã—ã¦ã„ã‚‹ã‹ï¼Ÿã«ã¤ã„ã¦ç´¹ä»‹ã—ã¾ã™ã€‚ 基本原ç†ã¨ã—ã¦ã¯ã€ã‚³ãƒ”ペãŒå¤šç™ºã™ã‚‹æ ¹ã£ã“ã§åˆ†å²ï¼ˆï¼ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©åˆ†å‰²ï¼‰ã˜ã‚ƒãªãã¦ã€å¿…è¦æœ€å°é™ã®ã¨ã“ã‚ã§é™å±€çš„ã«åˆ†å²ã™ã‚‹ã®ãŒã„ã„ã€ã¨ã„ã†è€ƒãˆæ–¹ã«åŸºã¥ãã¾ã™ã€‚ 一言ã§ã„ã†ã¨ã€ã€Œãƒ‘ラメー
リソースモデリングパターン
Webアプリケーションã«ã¤ã„ã¦ã€RESTfulãªURL・リソースè¨è¨ˆã®ãƒ‘ターンを見出ã™ã“ã¨ã§ã€ ã©ã®ãƒ‘ターンã‹ã‚’判æ–ã™ã‚‹ã ã‘ã§ã€æ—¢å˜ã® Good Practice ãŒé©ç”¨ã§ãã‚‹ åå‰ã‚’ã¤ã‘ã¦å‘¼ã¹ã‚‹ã‚ˆã†ã«ã—ãŸã„ Railsãªã©ã®ãƒ•ãƒ¬ãƒ¼ãƒ ワークã§ç°¡å˜ã«é©ç”¨ã§ãるよã†ã«ã—ãŸã„ ã¨ã„ã†ã“ã¨ã‚’目指ã—ã¦ã„ã¾ã™ã€‚ ã»ã‚“ã¨ã†ã«å½¹ç«‹ã¤ã‹ ã“ã‚Œã¯ãƒ‘ターンã¨è¨€ãˆã‚‹ã®ã‹ ã‚‚ã£ã¨ä»–ã«ã‚‚ã‚ã‚‹ ã ã„ã¶ç²’度ãŒãƒãƒ©ãƒãƒ© åå‰ã®ä»˜ã‘方（パターンã¯åå‰é‡è¦ï¼‰ ãªã©ã€ãœã²ã”æ„見をãã ã•ã„。 パターン Collection & Member Resource パターン Singular (Singleton) Resource パターン Filtered Collection パターン Filtered Subresource パターン Multi-member Resource パターン Partial Resource パター
JSON Pointerã¨JSON Patch - 一æ±ä¸‰èœ
XMLã®æ“作を標準化ã—ãŸç‰©ã¨ã—ã¦DOMやらXPathやらå„種è¦æ ¼ãŒå˜åœ¨ã™ã‚‹ã‚ã‘ã§ã™ãŒã€JSONã§ã‚‚ãã®ã‚ˆã†ãªã‚ˆã利用ã•ã‚Œã‚‹æ“作を共通化ã—ãŸç‰©ãŒå˜åœ¨ã™ã‚‹ã¨ä¾¿åˆ©ãªå ´é¢ã‚‚ã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 ãã“ã§IETFã®appsawg WGã§æ案ã•ã‚Œã¦ã„ã‚‹ã®ãŒã€JSON Pointerã¨JSON Patchã§ã™ã€‚ ã¾ã æ案ã•ã‚ŒãŸã°ã‹ã‚Šã§ã»ã¨ã‚“ã©ä½•ã‚‚決ã¾ã£ã¦ã„ãªã„ã®ãŒå®Ÿæƒ…ãªã®ã§ã™ãŒã€ã‚‚ã—RFCã¨ã—ã¦å…¬é–‹ã•ã‚Œã‚‹ã»ã©ã®ç‰©ãŒå‡ºæ¥ä¸ŠãŒã‚Œã°ã€æ¨™æº–çš„ãªæž 組ã¿ã¨ã—ã¦ã¯å¼·åŠ›ãªç‰©ã«ãªã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 JSON Pointer JSON Pointerã¯XMLã§è¨€ã†æ‰€ã®XLinkã¨XPathã®æ©Ÿèƒ½ã‚’ä½µã›æŒã£ãŸã‚ˆã†ãªç‰©ã§ã€JSONã®æ§‹é€ ã®ä¸ã®ã‚るオブジェクトを表ã™ã®ã«ç”¨ã„られãŸã‚Šã€URLä¸ã«ãŠã„ã¦fragment identifierã¨ã—ã¦ä½¿ã‚れる事ã§JSONã®æ§‹é€ ä¸ã®ç‰¹å®šã®ã‚ªãƒ–ジェクトを指ã—示ã™ã®ã«ä½¿ã‚れる事を想定ã—ã¦ã„ã¾ã™ã€‚
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ã€
routes.rb ã‚’ã‚‚ã†ä¸€åº¦è€ƒãˆã¦ã¿ãŸ #shibuyarb
The document discusses routes.rb in Rails applications. It notes that some developers find routes.rb confusing and messy. The document then analyzes some potential issues with routes.rb, including that the resources method is not very intuitive and that Rails routing is not fully convention over configuration. It also discusses prior work like Conventional Routes and Astaire that aimed to simplify
Making Rails Really restful
The document discusses making Rails applications more RESTful. It promotes improving resources in Rails by using the Restfulie plugin. The document advocates for consistency, simplicity and discoverability in RESTful design. However, it notes that just using HTTP verbs and pretty URLs does not necessarily make an application truly RESTful. It outlines the principles of REST including identifying r
RESTã®ã‚¤ãƒ³ãƒ”ーダンスミスマッãƒ
éžå®Ÿåœ¨naka aki @naka_aki_spl ã‚„ã£ã±ã‚ŠRESTã¨ã‹ã„ã£ã¦ã‚‹äººã‚‰ã¯GUIã‹ã‚‰èƒŒã‚’å‘ã‘ã‚‹ã‚“ã ã‚ã†ã‹ï¼Ÿé™çš„ãªè¦‹ãŸç›®ã¯ã„ãらã§ã‚‚GUIã«è¿‘ã¥ã‘られるã‘ã©ã€ãƒªã‚½ãƒ¼ã‚¹ã‚„URLã¨ã®çµ¡ã¿ã‚’考ãˆã‚‹ã¨æ™®é€šã®GUIã®ã‚‚ã®ã™ã”ãå°ã•ãªã€Œã‚µãƒ–セットã€ã«ãªã‚‹æ„Ÿã˜ã€‚ 2010-04-13 10:34:35
It is okay to use POST » Untangled
Tim Bray’s article on RESTful Casuistry revisits an odd meme in the REST debates that I’ve been meaning to discredit for a while. Some people think that REST suggests not to use POST for updates. Search my dissertation and you won’t find any mention of CRUD or POST. The only mention of PUT is in regard to HTTP’s lack of write-back caching. The main reason for my lack of specificity is because
第1回èªæ›¸ä¼š ã¾ã¨ã‚ - RESTfulèªæ›¸ä¼š
第1回èªæ›¸ä¼š ã¾ã¨ã‚ †以下ã®ã‚‚ã®ã¯ã‚ãã¾ã§ã‚‚スタッフ目線ã§ã™ã€‚å‚åŠ ã—ã¦ã„る方もãŒã‚“ãŒã‚“æ›´æ–°ã—ã¦ãã ã•ã„。（ãã“ã¯é•ã†ã‚“ã˜ã‚ƒã？ã¨ã„ã†ã®ã‚’ãŠå¾…ã¡ã—ã¦ã¾ã™ï¼‰ ↑ ç¾åœ°åˆ°ç€ã€œé–‹å ´ã€œè¨å–¶ †ç¾åœ°åˆ°ç€ 田町ã®èŠæµ¦å£ã‹ã‚‰æœ¬å½“ã«ã™ã ã“ã‚Œã¯ä¾¿åˆ©ã å ´æ‰€ã‚‚ã‚ã‹ã‚Šã‚„ã™ã„ é–‹å ´ãŒ15分é…ã‚Œ ä¼šå ´æ‰‹ç¶šãã‚’ã§ãるメンãƒãƒ¼ãŒé™ã‚‰ã‚Œã¦ã„ãŸãŸã‚ ä»–ã®äººã§ã‚‚ã§ããªã„ã‹ã‚’確èªã™ã‚‹ ã‚‚ã®ã™ã”ãã„ã„ä¼šå ´ è¨å‚™ãŒæ•´ã£ã¦ã„ã¦ã€ãã‚Œã„ã§ã‚‚ã®ã™ã”ãã„ã„ä¼šå ´ã§ã—ãŸã€‚ ã“ã‚“ãªä¼šå ´ã‚’使ãˆã‚‹ãªã‚“ã¦ã®ã¯ã‚„ã¯ã‚Šå¹¸é‹ã¨ã—ã‹ã„ã„よã†ãŒãªã„。 è¨å–¶ã«æ‰‹é–“å–ã‚‹ スタッフã®èª°ã‚‚ä¼šå ´ã®ä¸‹è¦‹ãŒã§ãã¦ã„ãªã‹ã£ãŸãŸã‚ã€ã©ã®ã‚ˆã†ã«ä½¿ç”¨ã™ã‚‹ã‹ã¨ã„ã†æ®µå–ã‚Šã‚‚å«ã‚ã¦è¡Œã£ãŸãŸã‚ ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®æº–å‚™ã«æ™‚é–“ãŒã¨ã‚‰ã‚Œã‚‹ çµå±€ä¼šå ´ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã¯ä½¿ãˆãšãƒ»ãƒ»ãƒ» 本当ã«ä½¿ç”¨ã§ããªã„ã‹ã¯ç¢ºèªã™ã¹ã 次回以é™ã¯e-mobileç‰ã‚’使ã†ã“ã¨ã‚‚検討 UStreamã§å‚åŠ ã™ã‚‹ã¤ã‚‚ã‚Šã ã£ãŸæ–¹
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Anemic REST | Technology Radar | Thoughtworks
EVOLVE`13 Keynote: Scrambled Eggs
リソースモデリングパターンã®æ案 #sendagayarb
http://capsctrl.que.jp/kdmsnr/diary/20080412.html
{{#tags}}- {{label}}
{{/tags}}