@@ -171,17 +171,17 @@ impl Launcher {
171171
172172 let processor = Processor :: new ( receiver. socket . clone ( ) , tracker. clone ( ) , cookie_lifetime) ;
173173
174- // We spawn the new task even if there active requests buffer is
175- // full. This could seem counterintuitive because we are accepting
176- // more request and consuming more memory even if the server is
177- // already busy. However, we "force_push" the new tasks in the
178- // buffer. That means, in the worst scenario we will abort a
179- // running task to make place for the new task.
180- //
181- // Once concern could be to reach an starvation point were we
182- // are only adding and removing tasks without given them the
183- // chance to finish. However, the buffer is yielding before
184- // aborting one tasks, giving it the chance to finish.
174+ /* We spawn the new task even if the active requests buffer is
175+ full. This could seem counterintuitive because we are accepting
176+ more request and consuming more memory even if the server is
177+ already busy. However, we "force_push" the new tasks in the
178+ buffer. That means, in the worst scenario we will abort a
179+ running task to make place for the new task.
180+
181+ Once concern could be to reach an starvation point were we are
182+ only adding and removing tasks without given them the chance to
183+ finish. However, the buffer is yielding before aborting one
184+ tasks, giving it the chance to finish. */
185185 let abort_handle: tokio:: task:: AbortHandle =
186186 tokio:: task:: spawn ( processor. process_request ( req, ban_service. clone ( ) ) ) . abort_handle ( ) ;
187187
0 commit comments