Injecting latency into application requests?

I think you'd want to call HTTP::collect with no collection size to hold the connection and then use 'after' to call HTTP::release. This is similar in concept to using HTTP::collect to hold the current request while you perform OCSP or other authentication.

 

 

I'm not sure how you could use 'after' by itself to stop the request from being sent to the pool or otherwise add latency. I could certainly be missing something on this though :)

 

 

Aaron