Chromium Code Reviews| Index: net/http/http_network_transaction.cc |
| diff --git a/net/http/http_network_transaction.cc b/net/http/http_network_transaction.cc |
| index b7ceb430bd9ea8bc3f1b202cdf7aaf483f3b4976..1e4dd45e1ad84f151d2fb824f2467d9566877173 100644 |
| --- a/net/http/http_network_transaction.cc |
| +++ b/net/http/http_network_transaction.cc |
| @@ -421,7 +421,13 @@ void HttpNetworkTransaction::PopulateNetErrorDetails( |
| void HttpNetworkTransaction::SetPriority(RequestPriority priority) { |
| priority_ = priority; |
| - // TODO: Note that if throttling is ever implemented below this |
| + // TODO(rdsmith): Handle race between SetPriority and |
| + // HttpStreamFactoryImpl::Job notifying this class of stream |
| + // creation (where this class will have set the priority on the |
| + // stream_request_ but that will be a no-op because the stream has |
| + // already been created). |
|
mmenke
2017/01/03 22:51:22
Think this should be clearer. I assume the issue
Randy Smith (Not in Mondays)
2017/01/05 03:47:18
Yep. I've reworded the comment; let me know what
|
| + |
| + // TODO(rdsmith): Note that if throttling is ever implemented below this |
|
mmenke
2017/01/03 22:51:22
Know this is an old comment, but I can't remember
Randy Smith (Not in Mondays)
2017/01/05 03:47:18
I've added " ... if *priority based* throttling ..
|
| // level, either of the two below calls may result in request |
| // completion, callbacks, and the potential deletion of this object |
| // (like the call below to throttle_->SetPriority()). In that case, |