// should probably start a goroutine to read from req. This best
				// effort select existed before the change to check 'deleted'.
				// But if we know for sure it wasn't deleted and a sender is
				// outstanding, we should probably block on req (in a new
				// goroutine) to get the connection back.
				select {
				default:
				case ret, ok := <-req:
					if ok && ret.conn != nil {

make(chan int, 100)
</pre>

<p>
The capacity, in number of elements, sets the size of the buffer in the channel.
If the capacity is zero or absent, the channel is unbuffered and communication
succeeds only when both a sender and receiver are ready. Otherwise, the channel
is buffered and communication succeeds without blocking if the buffer
is not full (sends) or not empty (receives).
A <code>nil</code> channel is never ready for communication.

9620253,"touches":1,"min_t":1236222384,"max_t":1236222384,"mean_t":1236222384},{"name":"onload-re-entry-expected.txt","kids":[],"cl_weight":0.002531645569620253,"touches":1,"min_t":1236222384,"max_t":1236222384,"mean_t":1236222384},{"name":"event-sender-mouse-moved-expected.png","kids":[],"cl_weight":0.0006270059426999707,"touches":2,"min_t":1228525763,"max_t":1236205616,"mean_t":1232365689},{"name":"event-listener-on-link-expected.png","kids":[],"cl_weight":0.0006270059426999707,"touches":2,"mi...