知ã£ã¦ã„るよã†ã§çŸ¥ã‚‰ãªã„Webサーãƒã‚¢ãƒ¼ã‚テクãƒãƒ£
第６回ゲームサーãƒå‹‰å¼·ä¼šç”¨è³‡æ–™ã§ã™ã€‚ Webã®æŠ€è¡“ã®æ ¹å¹¹ã¨ãªã‚‹HTTPã‚„TCP/IPを軽ããŠã•ã‚‰ã„ã—ãŸã‚ã¨ã€ マルãƒãƒ—ãƒã‚»ã‚¹ã€ãƒžãƒ«ãƒã‚¹ãƒ¬ãƒƒãƒ‰ã€ã‚¤ãƒ™ãƒ³ãƒˆé§†å‹•ã¨ã„ã£ãŸã‚µãƒ¼ãƒã‚¢ãƒ¼ã‚テクãƒãƒ£ã«ã¤ã„ã¦è§£æžã—〠ã•ã‚‰ã«ã‚¤ãƒ™ãƒ³ãƒˆé§†å‹•ã‚’実ç¾ã™ã‚‹ãŸã‚ã®éžãƒ–ãƒãƒƒã‚ングI/Oã¨I/Oã®å¤šé‡åŒ–ã«ã¤ã„ã¦è§£èª¬ã—ã¾ã™ã€‚
HTTP APIã®è©³ç´°ãªã‚¨ãƒ©ãƒ¼æƒ…å ±ã‚’ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã«æŒãŸã›ã‚‹ãŸã‚ã®ä»•æ§˜
今日ã§ã¯ HTTP(s) 㧠API ãŒå…¬é–‹ã•ã‚Œã‚‹ã“ã¨ã¯å½“ãŸã‚Šå‰ã®æ™‚代ã§ã™ãŒã€ã‚¨ãƒ©ãƒ¼ã‚’アプリケーションã«ã©ã†ä¼ãˆã‚‹ã‹ã¯ã€å€‹ã€…ã® API ã®è¨è¨ˆã«ä¾å˜ã—ã¦ã„ã¾ã—ãŸã€‚特ã«ã€HTTP ステータスコードã¯æœ‰é™ã§ã‚ã‚Šã€å…ƒã€…æŒã£ã¦ã„ã‚‹æ„味ãŒã‚ã‚‹ã®ã§ã€è‡ªç”±ã«ä½¿ã†ã“ã¨ã¯ã§ãã¾ã›ã‚“。API ã¯ãã®ãƒ‰ãƒ¡ã‚¤ãƒ³ã”ã¨ã«ã‚‚ã£ã¨è¤‡é›‘ã§ç´°ã‹ãªã‚¨ãƒ©ãƒ¼æƒ…å ±ãŒã‚ã‚‹ã¯ãšã§ã€ãれらã¯ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒœãƒ‡ã‚£ã«è¼‰ã›ã¦ã‚¢ãƒ—リケーションã«ä¼ãˆã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ãŒã€ãã®æ›¸å¼ã«è¦å®šã¯ä»Šã¾ã§ã‚ã‚Šã¾ã›ã‚“ã§ã—ãŸã€‚ HTTP API ã«ã¦ã€ã‚¢ãƒ—リケーションã«ã‚¨ãƒ©ãƒ¼æƒ…å ±ã‚’ä¼é”ã™ã‚‹ãŸã‚ã®ï¼ˆãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒœãƒ‡ã‚£ã«è¼‰ã›ã‚‰ã‚Œã‚‹ï¼‰æ¨™æº–çš„ãªå½¢å¼ãŒã€RFC7807 Problem Details for HTTP APIs ã§å®šã‚られã¦ã„ã¾ã™ã€‚é©ç”¨ä¾‹ã¨ã—ã¦ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚ HTTP/1.1 403 Forbidden Content-Type: application
Chrome Extensionã®Live HTTP Headersã®èª¿æŸ»(CoolBar.Proå°Žå…¥ ExtensionãŒä½•ã‚’è¡Œã†ã‹ã®èª¿æŸ»)
a.md Chrome Extensionã®Live HTTP Headersを調査ã—ãŸã€‚Firefox用ã®ã‚‚ã®ã§ã¯ãªã„。Firefox用ã®ã‚‚ã®ã§ã¯ãªã„。 https://chrome.google.com/webstore/detail/live-http-headers/iaiioopjkcekapmldfgbebdclcnpgnlo 11/7追記 é¡žä¼¼ or åŒæ§˜ã®æ–¹æ³•ã§é›£èªåŒ–scriptを埋ã‚込んã§ã„る拡張機能ãŒå¤§é‡ã«ã‚ã£ãŸãŸã‚ã€Googleã«å ±å‘Šæ¸ˆã¿ã€‚ https://twitter.com/bulkneets/status/795260268221636608 English version: https://translate.google.com/translate?sl=ja&tl=en&js=y&prev=_t&hl=ja&ie=UTF-8&u=https%3A%2F%
Elixir ã®ãƒ—ãƒã‚»ã‚¹ã‚’使ã£ã¦ãƒ•ã‚§ã‚¤ãƒ«ã‚»ãƒ¼ãƒ•ãªã‚¢ãƒ—リケーションを作る ─ 失敗ã¯æã‚Œãšæ³¥æ°´ã«ãƒ€ã‚¤ãƒ– - Qiita
[翻訳] Elixirã®ãƒ—ãƒã‚»ã‚¹ã‚¢ãƒ¼ã‚テクãƒãƒ£ ã¾ãŸã¯ç§ã¯å¦‚何ã«ã—ã¦å¿ƒé…ã™ã‚‹ã®ã‚’æ¢ã‚ã¦ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã‚’æ„›ã™ã‚‹ã‚ˆã†ã«ãªã£ãŸã‹ ã«ã‚‚ã‚るよã†ã« Elixir ã«ãŠã„ã¦ã¯ä¾‹å¤–処ç†ã¯ã€ãã‚Œã‚’é ‘å¼µã£ã¦ãªã‚“ã¨ã‹ã—よã†ã¨ã™ã‚‹ã®ã§ã¯ãªãã€è»½é‡ãƒ—ãƒã‚»ã‚¹ã®ã‚³ãƒ³ãƒ†ã‚ストã§ã‚€ã—ã‚ã™ã™ã‚“ã§ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã•ã›ã¦ã—ã¾ãˆã€ã¨ã„ã†ã®ãŒè‰¯ã„作法ã§ã‚る。 クイズ番組㧠○ ㋠× ã‹ç”ãˆã‚’é¸ã‚“ã§å£ã«çªã£è¾¼ã‚“ã å…ˆã«ã€æ£è§£ãªã‚‰ã‚¯ãƒƒã‚·ãƒ§ãƒ³ãŒã€ä¸æ£è§£ãªã‚‰æ³¥æ°´ãŒã‚ã‚‹ã¨ã„ã†ä¼ç”»ãŒã‚ã‚‹ãŒã€ãã‚Œã«å–©ãˆã‚‹ãªã‚‰ 泥水ã ã‚ã†ãŒä½•ã ã‚ã†ãŒèºŠèº‡ã›ãšãƒ€ã‚¤ãƒ–ã—ã‚! ã¨ã„ã†ã®ãŒ Elixir æµ (俺調ã¹) ã§ã‚る。 ã‚‚ã¨ã„ã€ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã•ã›ã¦ã©ã†ã™ã‚‹ã®ã‹ã¨ã„ã†ã¨ Supevisor を使ã£ã¦ã€åˆ¥ãƒ—ãƒã‚»ã‚¹ã‹ã‚‰è©²å½“プãƒã‚»ã‚¹ã‚’監視ã—ã¦ãŠã„ã¦ã€ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã—ã¦ã‚‚アプリケーション全体ã¨ã—ã¦ã¯é–“é•ã„ãªãå‹•ã„ã¦ã„る状態をä¿è¨¼ã™ã‚‹ã®ãŒæ£ã—ã„。 カッã¨ãªã£ã¦ã¡ã‚‡ã£ã¨ãã®ãŸã‚ã®ä¾‹ã‚’書ã„ã¦
ソースã«ä¸€è¡Œè¿½åŠ ã™ã‚‹ã ã‘ã§ã™ã¹ã¦ã® HTTP 通信をãƒã‚®ãƒ³ã‚°ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’書ã„㟠#golang - è©©ã¨å‰µä½œãƒ»æ€ç´¢ã®ã²ã‚ã°
ã“ã¡ã‚‰ã§ã™ã€‚Perl ã§ã„ã†ã¨ Devel::KYTProf ã«æ€§è³ªãŒã¡ã‹ã„。 motemen/go-loghttp · GitHub (GoDoc) 使用例 ãŸã¨ãˆã°ã“ã†ã„ã†ã‚³ãƒ¼ãƒ‰ã«â€¦ package main import ( "io" "log" "net/http" "os" ) func main() { resp, err := http.Get(os.Args[1]) if err != nil { log.Fatal(err) } io.Copy(os.Stdout, resp.Body) } % go run main.go http://example.com/ <!doctype html> ... ä¸€è¡Œè¿½åŠ ã™ã‚‹ã¨: package main import ( "io" "log" "net/http" "os" _ "github.com/motemen/go-lo
Rails API Testing Best Practices · Matthew Lehner
Something went wrong! Hang in there while we get back on track Writing an API is almost a given with modern web applications. I’d like to lay out some simple guidelines and best practises for Rails API testing. We need to determine what to test and why it should be tested. Once we’ve established what we will be writing tests for, we will set up RSpec to do this quickly and easily. Basically we’ll
HTTPリクエストを減らã™ãŸã‚ã«ã€åºç« 】HTTPリクエストã¯ç”˜ãˆ - MOL
ã“ã®ã‚·ãƒªãƒ¼ã‚ºã¯HTTPリクエストã®ç†è§£ã‚’通ã˜ã¦Webパフォーマンスã®é‡è¦æ€§ã«ã¤ã„ã¦è€ƒãˆã‚‹5ç« æ§‹æˆã«ãªã£ã¦ã„る。 ã€åºç« 】HTTPリクエストã¯ç”˜ãˆ ã€CSS Sprite編】スプライト地ç„ã‹ã‚‰ã®è§£æ”¾ ã€WebFont編】ドラッグ＆ドãƒãƒƒãƒ—ã—ã¦ã‚³ãƒžãƒ³ãƒ‰å©ã„ã¦ã‚¦ã‚§ãƒ¼ã‚¤ ã€DataURI編】é…延ãƒãƒ¼ãƒ‰ã§ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ãƒ–ãƒãƒƒã‚¯ã‚’å›žé¿ ã€çµ‚ç« ã€‘æˆ‘ã€…ã«ã¯1000msã®çŒ¶äºˆã—ã‹æ®‹ã•ã‚Œã¦ã„ãªã„ 1日目ã¯ã€HTTPリクエストã®æ¦‚è¦ã«ã¤ã„ã¦èª¬æ˜Žã™ã‚‹ã€‚ 例ãˆã«ã€ç§ã®ãƒãƒ¼ãƒˆãƒ•ã‚©ãƒªã‚ªãƒšãƒ¼ã‚¸ï¼ˆt32k.me）ãŒè¡¨ç¤ºã•ã‚Œã‚‹ã¾ã§ã®æµã‚Œã‚’見ã¦ã„ã。ã¾ãšã€æ¤œç´¢ã‹ã‚‰ã§ã‚‚方法ã¯ãªã‚“ã§ã‚‚よã„ãŒã€ãƒ–ラウザã®URLãƒãƒ¼ã«t32k.meã¨æ‰“ã¡è¾¼ã‚“ã§ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã€‚ãã®ãƒšãƒ¼ã‚¸ã‚’見ã«ã„ãã¨ã„ã†ã“ã¨ã¯ã€ã¤ã¾ã‚Št32k.meã«å¯¾ã—ã¦HTTPスã‚ームã§ãƒªã‚¯ã‚¨ã‚¹ãƒˆã™ã‚‹ã¨ã„ã†ã“ã¨ã‚’æ„味ã—ã¦ã„る。 クライアントã§ã‚るブラウザã¯å…¥åŠ›ã•ã‚ŒãŸURLを判æ–ã—ã¦ã€ãƒªã‚½
Big Sky :: httpstatus コマンドã§ã€HTTP ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ã™ã°ã‚„ãã—らã¹ã‚‹!
一般的㪠Web Programmer ãªã‚‰ã°ã€HTTP Status code ã¯ã™ã¹ã¦æš—記ã—ã¦ã„ã‚‹ã¨èžãã¾ã—ãŸã€‚ ã—ã‹ã—ã€åƒ•ã¯åˆå¿ƒè€…ãªã®ã§ã€ãªã‹ãªã‹è¦šãˆãã‚Œã¦ã„ãªã„ã®ã§ã€HTTPã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ã•ãŒã™ã®ã«ä¾¿åˆ©ãªãƒ„ールを用æ„ã—ã¾ã—ãŸã€‚ httpstatus-vim ã§ã™ã€‚インストール方法㯠bundle ã‹ãªã‚“ã‹ã§ä»¥ä¸‹ã‚’è¿½åŠ ã—ã¦ä¸‹ã•ã„。 mattn/httpstatus-vim - GitHub https://github.com/mattn/httpstatus-vim 使ã„æ–¹ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚ 4xx ãªã‚³ãƒ¼ãƒ‰ã‚’列挙ã™ã‚‹ã€‚ :HttpStatus 4 400: Bad Request 401: Unauthorized 402: Payment Required 403: Forbidden 404: Not Found 405: Method Not Allowed 406
httpstatus コマンドã§ã€HTTP ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ã™ã°ã‚„ãã—らã¹ã‚‹! - tokuhirom's blog
一般的㪠Web Programmer ãªã‚‰ã°ã€HTTP Status code ã¯ã™ã¹ã¦æš—記ã—ã¦ã„ã‚‹ã¨èžãã¾ã—ãŸã€‚ ã—ã‹ã—ã€åƒ•ã¯åˆå¿ƒè€…ãªã®ã§ã€ãªã‹ãªã‹è¦šãˆãã‚Œã¦ã„ãªã„ã®ã§ã€HTTPã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ã•ãŒã™ã®ã«ä¾¿åˆ©ãªãƒ„ールを用æ„ã—ã¾ã—ãŸã€‚App::httpstatus ã§ã™ã€‚インストール方法㯠cpanm App::httpstatus ã§ã™ã€‚ã¨ã„ã†ã‹ä¾å˜ã¨ã‹ãªã„ã®ã§http://api.metacpan.org/source/TOKUHIROM/App-httpstatus-v1.0.0/httpstatus をコピーã—ã¦ãã‚Œã°ã†ã”ãã¾ã™ã€‚ 使ã„æ–¹ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚ 4xx ãªã‚³ãƒ¼ãƒ‰ã‚’列挙ã™ã‚‹ã€‚ % httpstatus 4 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Foun
SPDYã¨ã€Œã‚„ã£ãŸãƒ¼ã€net-http-spdyã§ããŸã‚ˆãƒ¼ã€ã®è©± - I am Cruby!
SPDYを知るSPDYã¨ã„ã†å®Ÿé¨“çš„ãªãƒ—ãƒãƒˆã‚³ãƒ«ãŒã‚ã‚Šã¾ã—ã¦ã€ SPDY - The Chromium Projects HTTP2.0ã¯SPDYをベースã«ä½œã‚‰ã‚Œã‚‹ã‹ã‚‚ã€ã¿ãŸã„ãªè©±ã‚‚風ã®å™‚ã§èžã„ãŸã‚Šã™ã‚‹ã®ã§ã˜ã‚ƒã‚ã©ã‚“ãªã‚‚ã‚“ã‹ãªã‚ã¨ä»•æ§˜ã‚’èªã‚“ã§è¦‹ã¾ã—ãŸã€‚ SPDY Protocol - Draft 2 - The Chromium Projects SPDY Protocol - Draft 3 - The Chromium Projects SPDYv2ã¨SPDYv3ã¨ã„ã†ã®ãŒã‚ã£ã¦ã€åŸºæœ¬çš„ã«ã¯SPDYv3ã®æ–¹ã‚’èªã‚“ã©ã‘ã°ã„ã„ã®ã‹ãªã‚ã¨ã¯æ€ã„ã¾ã™ã€‚ ãŸã SPDYv2ã‚‚ã™ã§ã«ã„ã‚ã‚“ãªã¨ã“ã‚ã§ä½¿ã‚ã‚Œã¦ã„ã¾ã™ã®ã§ã€ä»•æ§˜æ›¸ã®ã€Œ7.Incompatibilities with SPDY draft #2ã€ã®éƒ¨åˆ†ã‚‚ãƒã‚§ãƒƒã‚¯ã—ã¦ãŠãã¾ã—ょã†ã€‚ HTTP Layering over SPDYSPDYã¨ã„ã†ã®
ã¾ãŸã¤ã¾ã‚‰ã¬Gemを作ã£ã¦ã—ã¾ã£ãŸâ€¦ - I am Cruby!
先週ã¨ä»Šé€±ã§å¤œãªã¹ã—ã¦2ã¤ã»ã©ã¤ã¾ã‚‰ã¬Gemを作りã¾ã—ãŸã€‚ã¾ãšä¸€ã¤ç›®ã€‚ ScrymScrymã¨ã„ã†ã‚„ã¤ã§ã™ã€‚ authorNari/scrym ? GitHub http://rubygems.org/gems/scrym Scrymã¯Self collecting Ruby Mutatorsã¨ã„ã†åå‰ã®ç•¥ã§ã™ã€‚ 何をã™ã‚‹ã‹ã¨ã„ã†ã¨ã€malloc/freeã¿ãŸã„ãªã®ã‚’簡易的ãªMarkSweepã§ã‚„ã‚‹ã‚„ã¤ãªã‚“ã§ã™ã。 CRubyã«ã¯GCãŒã‚ã‚Šã¾ã™ãŒã€Scrym::Mutator.mark(obj)ã¨ã‹ã™ã‚‹ã¨å¯¾è±¡ã®objã¯GCã‹ã‚‰ï¼ˆã»ã¼ï¼‰ç®¡ç†ã•ã‚Œãªããªã‚Šã€ãã®ä»£ã‚ã‚Šã«Scrym::Mutator.collectã®å¯¾è±¡ã¨ãªã‚Šã¾ã™ã€‚ ãµã¤ã†ã®MarkSweepã¿ãŸãScrym::Mutator.collectã¨æ¬¡ã®collectã®é–“ã§markã—ã¦ãŠã‘ã°ãã®ã‚ªãƒ–ジェクトã¯æ¶ˆã•ã‚Œãªã„ã—ã€markã—ãªã‘
ウェブエンジニアã®ãŸã‚ã®ã‚ªãƒ³ãƒ©ã‚¤ãƒ³ãƒ„ールã¾ã¨ã‚
The Web engineer's online toolboxã¨ã„ã†ã¾ã¨ã‚記事ãŒä¾¿åˆ©ãã†ã ã£ãŸã®ã§ã€å®Ÿéš›ã«è©¦ã—ã¤ã¤æŠ„訳ã—ã¦ã¿ã¾ã—ãŸã€‚(一部ã®ã‚³ãƒ¡ãƒ³ãƒˆã¨ä½“è£ã¯å¤‰ãˆã¦ã„ã¾ã™ã€‚) 目次 一覧 RequestBin httpリクエストをä¿å˜ã™ã‚‹ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã‚’作ã£ã¦ãれる。 Create a RequestBin ã®ãƒœã‚¿ãƒ³ã‚’クリックã™ã‚‹ã¨URLãŒè¡¨ç¤ºã•ã‚Œã‚‹ã®ã§ã€ãã“ã‚’HTTPクライアントã‹ã‚‰ãŸãŸãã¨RequestBinå´ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆå†…容ãŒè¨˜éŒ²ã•ã‚Œã‚‹ã€‚ ソースも公開ã•ã‚Œã¦ã‚‹ã®ã§ãƒãƒ¼ã‚«ãƒ«ã§ç«‹ã¡ã‚ã’ã‚‹ã“ã¨ã‚‚ã§ãる。 githubã®webhookã®helpã‚‚å‚考ã«ã©ã†ãžã€‚ Hurl httpリクエストを実行ã—ã¦ãれる。パーマリンクも作ã£ã¦ãれるã®ã§ã€POSTリクエストもコピペã§ä»–ã®äººã¨å…±æœ‰ã§ãる。 類似サービス: REST test test , Apigee console httpbin HTTP
HTTP Status Codes Glossary
HTTP status codes are three-digit numbers that are returned by servers to indicate the status of a client’s request. When a client (such as a web browser) makes a request to a server, the server will respond with a status code and a message indicating whether the request was successful or not. There are five classes of HTTP status codes, each identified by the first digit of the three-digit status
500,000 requests/sec – Modern HTTP servers are fast
A modern HTTP server running on somewhat recent hardware is capable of servicing a huge number of requests with very low latency. Here’s a plot showing requests per second vs. number of concurrent connections for the default index.html page included with nginx 1.0.14. With this particular hardware & software combination the server quickly reaches over 500,000 requests/sec and sustains that with gr
POSTå¯èƒ½ãªRubyã®Net::HTTPå½è£…テストライブラリWebMock - ããŸã‚‚ã‚‚ã‚“ãŒãŒããŸã‚“。
水風呂ã®ã™ã‚゠毎日ã‚ã¡ã‚ƒãã¡ã‚ƒã«æš‘ã„。 ã“ã“数年「ãŠã‚ˆã’!ãŸã„ã‚„ããã‚“ã€ã®ã‚ˆã†ã«æ˜¼é–“ã¯å¤ªé™½ã¨ã‚ªãƒ•ã‚£ã‚¹ãƒ“ルã¨ã‚¢ã‚¹ãƒ•ã‚¡ãƒ«ãƒˆã®ä¸‰æ–¹å‘ã‹ã‚‰æŠ¼ã—寄ã›ã‚‹35℃オーãƒãƒ¼ã®ç†±ã«æŒŸã¾ã‚Œã€å¤œã«ãªã£ã¦ã‚‚最低気温ãŒ27℃ãらã„ã¾ã§ã—ã‹ä¸‹ãŒã‚‰ãªã„。ãã‚“ãªç†ä¸å°½ãªæ±äº¬é‹ã®ä¸ã®æš®ã‚‰ã—ãŒæ¯Žå¹´ã®ã“ã¨ã«ãªâ€¦
Ruby ã§é«˜é€Ÿã« OAuth ã§èªè¨¼ã—㦠アクセス ã™ã‚‹æ–¹æ³• - Candy
çµè«–ã‹ã‚‰è¨€ã†ã¨ã€å¼·åŠ›ãª CPU ã¨å¤§å®¹é‡ã®ãƒ¡ãƒ¢ãƒªã‚’用æ„ã—㦠Thread を大é‡ã«ä½œã‚‹ã®ãŒä¸€ç•ªé€Ÿã„。 ã ã•ã„ã“ã¨ã“ã®ä¸Šç„¡ã„ãŒã€ã“ã‚ŒãŒé€Ÿã„ã‚“ã ã‹ã‚‰ä»•æ–¹ãªã„。 def self.post tokens = [] User.all.each do |u| tokens << OAuth::AccessToken.new(consumer, u.token, u.secret_token) end tokens.each do |a| @t = Thread.start do res = a.post('/statuses/update.json', {:status => "ãªã‚‹ã»ã©å››æ™‚ã˜ã‚ƒãーã®"}) rescue nil end end @t.join end ã“ã‚“ãªã®ã€‚本当ã«ã ã•ã„ã®ã ã‘ã©ã€ã“ã‚Œã§å分ãªã®ã ã‹ã‚‰ã—ょã†ãŒãªã„。ã¨ã„ã†ã‹ Ruby ã§ã‚„ã‚‹é™ã‚Šã“ã‚ŒãŒä¸€ç•ªé€Ÿã„。ã†ã¡ã®ãã‚Œãªã‚Šã®ã‚µãƒ¼
Linux ã§ã ã£ã¦ Fiddler ã—ãŸã„ - oogatta ã®ãƒ–ãƒã‚°
Fiddler @sugamasao 先生もブãƒã‚°ã«æ›¸ã„ã¦ã‚‰ã£ã—ゃる Fiddler ã¯ã€å…¨ Web 開発者必æºã®ãƒ„ールã¨ã‚‚言ãˆã‚‹æœ€é«˜ã® HTTP プãƒã‚ã‚·ã¨ã„ã†ã‹ HTTP スプーフィング・モニターツールã§ã™ãŒã€ãªã‚“ãŸã‚‹ã“ã¨ã‹ MS 様謹製ゆãˆã® Windows Only 。 ã¨ã“ã‚ãŒåƒ•ã¯ä»Šã‚„会社も自宅も Ubuntu ã¾ãŸã¯ OpenBSD ã§ã‚る生粋㮠Unix ライクシステム野郎ã§ã‚り〠Fiddler ã¤ã‹ãˆãªã„ï¼ã€‚ã‚ã‚‹ã®ã¯ WireShark ã ã‘ï¼ã€‚硬派ã™ãŽã‚‹ï¼ã€‚レイヤー低ã™ãŽã‚‹ï¼ã€‚ã‚‚ã£ã¨ã“ã†ãã€ã‚ã‹ã‚‹ã§ã—ã‚‡ï¼Ÿã€‚ç´ ç›´ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆã¨ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã¯ã¾ã¨ã¾ã£ã¦ã¦æ¬²ã—ã„ã§ã™ã—ã€ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãŒ JSON ã¨ã‹ XML ã ã£ãŸã‚‰ç‰¹åˆ¥ãªãƒ“ューワã§ç´ 敵ã«è¡¨ç¤ºã—ã¦æ¬²ã—ã„ã§ã™ã—ã€ãƒãƒãƒãƒã¨ GUI ã§å†ãƒªã‚¯ã‚¨ã‚¹ãƒˆã—ãŸã‚Šã¡ã‚‡ã£ã¨ãƒªã‚¯ã‚¨ã‚¹ãƒˆã®å†…容変ãˆã¦ã¿ãŸã‚Šãƒ¬ã‚¹ãƒãƒ³ã‚¹å·®ã—替ãˆã¦ã¿ãŸã‚Šã‚«ã‚¸ãƒ¥ã‚¢ãƒ«æ„Ÿè¦šã§ H
Githubをファイアウォールã®å†…å´ã‹ã‚‰ä½¿ãˆã‚‹ã‚ˆã†ã«ãªã£ãŸ - idesaku blog
Githubã¯ã€ã‚‚ã¯ã‚„ファイアウォールã®å†…å´ã§ã‚ã£ã¦ã‚‚read-onlyã§ã¯ãªã„。 From now on, if you clone a repository over the http:// url and you are using a Git client version 1.6.6 or greater, Git will automatically use the newer, better transport mechanism. Even more amazing, however, is that you can now push over that protocol and clone private repositories as well. Smart HTTP Support | The GitHub Blog Githubã¯ã™ã°ã‚‰ã—ã„サービスãªã®ã ãŒã€æ•°å°‘ãªã„æ¬
ランã‚ング
ãŠçŸ¥ã‚‰ã›
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
composerã®é…ã•ã‚’ã¾ã˜ã‚ã«è€ƒãˆã‚‹ #phpstudy
http://coderepos.org/share/browser/lang/ruby/cocproxy
{{#tags}}- {{label}}
{{/tags}}