Dirk Bolte
07/28/2023, 8:25 AMafterComplete
are not processed timely. Can it happen that these events are processed after the response was sent and thus even after the next request is matched?Oleg Nenashev
07/28/2023, 8:35 AMDirk Bolte
07/28/2023, 8:37 AMOleg Nenashev
07/28/2023, 8:43 AMTom
07/31/2023, 10:17 AMafterComplete
only occurs after the response has been fully sent.
So there’s no way to make this synchronous unfortunately. Jetty did have a blocking IO connector a few versions ago but they dropped it IIRC.
I suggest using afterMatch
if you can as this is (or should be!) reliably synchronous.Dirk Bolte
07/31/2023, 10:19 AMafterMatch
?Tom
07/31/2023, 10:23 AMDirk Bolte
07/31/2023, 10:24 AMTom
07/31/2023, 10:24 AMafterResponseRendered
Dirk Bolte
07/31/2023, 10:25 AMbeforeComplete
?Tom
07/31/2023, 10:26 AMbeforeComplete
is a bit ambiguous i.e. how far before complete are we?Dirk Bolte
07/31/2023, 10:29 AMTom
07/31/2023, 10:31 AMbeforeResponseSent
as the best place to call it seems to be after response rendering + all other activities have taken place. Does this seem reasonable to you?Dirk Bolte
07/31/2023, 10:32 AMTom
07/31/2023, 11:39 AMDirk Bolte
07/31/2023, 11:39 AMTom
07/31/2023, 11:39 AMDirk Bolte
08/02/2023, 9:00 AMTom
08/02/2023, 10:03 AM