You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
I'd like to use the Client API code for writing a loadtest suite. To make this work well, I would need it to use a customized "request" module object that can monitor and report on each outgoing HTTP request.
I made a first pass at this in the following commit, but it's pretty inelegant:
@rfk I don't see anything wrong with your approach, however an alternative would be to make ClientApi an EventEmitter. I've used that approach for diagnostics before, in poolee for instance.
EventEmitter +1, that sounds a lot cleaner from an API standpoint. I'll continue with my hacked up version for now, and we can consider a more holistic refactoring sometime soon.
I'd like to use the Client API code for writing a loadtest suite. To make this work well, I would need it to use a customized "request" module object that can monitor and report on each outgoing HTTP request.
I made a first pass at this in the following commit, but it's pretty inelegant:
007a390
You can see how I intend to use such functionality here:
4c1fca7#L2R14
@dannycoates @zaach thoughts on the best way to achieve such functionality?
The text was updated successfully, but these errors were encountered: