Hello,
I wonder if the existing implemented logic of suspending and resuming a
fiber is correct. Intuitively, I would expect that a fiber suspended
during a request processing would, after resuming, continue with a call
to next.processRequest(...)[1], which is not the currently implement
behavior (right now the resumed fiber ignores next tube and immediately
calls processResponse() on the last tube in the stack - the one that
suspended the fiber). IOW, currently the request processing cannot be
really suspended as resume is available only for response processing.
I would like to ask if you could change the existing implementation to
allow the "natural" suspend behavior. Shall I file a RFE?
Thank you,
Marek
[1] I have a use case where I would like to use this suspend behavior.