Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for badly (0.04 sec)

  1. src/net/http/serve_test.go

    // Note that this does not test the "request too large"
    // exit path from the http server. This is intentional;
    // not sending Connection: close is just a minor wire
    // optimization and is pointless if dealing with a
    // badly behaved client.
    func TestHTTP10ConnectionHeader(t *testing.T) {
    	run(t, testHTTP10ConnectionHeader, []testMode{http1Mode})
    }
    func testHTTP10ConnectionHeader(t *testing.T, mode testMode) {
    	mux := NewServeMux()
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri Jun 07 17:57:01 UTC 2024
    - 202K bytes
    - Viewed (0)
  2. src/runtime/proc.go

    // (2) for optimal thread management we would need to know the future (don't park
    // a worker thread when a new goroutine will be readied in near future).
    //
    // Three rejected approaches that would work badly:
    // 1. Centralize all scheduler state (would inhibit scalability).
    // 2. Direct goroutine handoff. That is, when we ready a new goroutine and there
    //    is a spare P, unpark a thread and handoff it the thread and the goroutine.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 29 17:58:53 UTC 2024
    - 207.5K bytes
    - Viewed (0)
  3. src/net/http/transport_test.go

    		didreq <- true
    	}()
    	unblockCh <- true
    	<-didreq
    }
    
    // Test that the transport doesn't close the TCP connection early,
    // before the response body has been read. This was a regression
    // which sadly lacked a triggering test. The large response body made
    // the old race easier to trigger.
    func TestIssue3644(t *testing.T) { run(t, testIssue3644) }
    func testIssue3644(t *testing.T, mode testMode) {
    	const numFoos = 5000
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Thu Jun 06 21:59:21 UTC 2024
    - 192.6K bytes
    - Viewed (0)
Back to top