When considering this issue alongside with RFD 397, it seems to me that the problem is actually using future drops as an implicit (!) cancellation signal. This makes drop handlers responsible for handling every…
Yes, but since they control the background service too, they can just update the service to make it respond to CORS requests.
This DOES need to be put into context. It is very, VERY old, so old it even predates all modern congestion control algorithms. The timer problems were solved by Van Jacobson in 1988, who replaced the fixed beta…
When considering this issue alongside with RFD 397, it seems to me that the problem is actually using future drops as an implicit (!) cancellation signal. This makes drop handlers responsible for handling every…
Yes, but since they control the background service too, they can just update the service to make it respond to CORS requests.
This DOES need to be put into context. It is very, VERY old, so old it even predates all modern congestion control algorithms. The timer problems were solved by Van Jacobson in 1988, who replaced the fixed beta…