From 6ddb6727c21bd82fdb3276808e01a1822d50798a Mon Sep 17 00:00:00 2001 From: jasonjkeller Date: Thu, 5 Oct 2023 10:45:50 -0700 Subject: [PATCH] Update readme --- instrumentation/jetty-9.3/README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/instrumentation/jetty-9.3/README.md b/instrumentation/jetty-9.3/README.md index a11720350d..31562a22df 100644 --- a/instrumentation/jetty-9.3/README.md +++ b/instrumentation/jetty-9.3/README.md @@ -3,9 +3,6 @@ This describes the basic behavior of an async request made using the Jetty Continuations or Servlet async API with Jetty as the dispatcher - -To be clear, we do not instrument the continuations API and we have no idea if undispatch is being called, we simply keep track of state based on what Jetty is doing with the request, what the AsyncContext being passed across threads tells us, and what notifications the AsyncListener we registered gets about the result of the async operation. - ## Request Flow The basic flow of an async request using continuations/async servlet API and being handled by Jetty is something like this: