Remove obsolete note in the docs
The Stream implementationa also wants you to take care of managing capacity yourself.
This commit is contained in:
		
				
					committed by
					
						 Sean McArthur
						Sean McArthur
					
				
			
			
				
	
			
			
			
						parent
						
							c3bc09550e
						
					
				
				
					commit
					869e7162c4
				
			| @@ -125,11 +125,6 @@ pub struct StreamId(u32); | |||||||
| /// See method level documentation for more details on receiving data. See | /// See method level documentation for more details on receiving data. See | ||||||
| /// [`FlowControl`] for more details on inbound flow control. | /// [`FlowControl`] for more details on inbound flow control. | ||||||
| /// | /// | ||||||
| /// Note that this type implements [`Stream`], yielding the received data frames. |  | ||||||
| /// When this implementation is used, the capacity is immediately released when |  | ||||||
| /// the data is yielded. It is recommended to only use this API when the data |  | ||||||
| /// will not be retained in memory for extended periods of time. |  | ||||||
| /// |  | ||||||
| /// [`client::ResponseFuture`]: client/struct.ResponseFuture.html | /// [`client::ResponseFuture`]: client/struct.ResponseFuture.html | ||||||
| /// [`server::Connection`]: server/struct.Connection.html | /// [`server::Connection`]: server/struct.Connection.html | ||||||
| /// [`FlowControl`]: struct.FlowControl.html | /// [`FlowControl`]: struct.FlowControl.html | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user