Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the discussion in #9 this PR adds a new Fluent response API, replacing the current overload based API.
JSON
Additionally, it adds capabilities to simulate network latency:
And network transfer rates (only with streams):
Furthermore,
.TimesOut
andTimesOutAfter
alternatives have been renamed to.ClientTimeout()
. A.ServerTimeout()
was also added which instead of throwing aTaskCancelledException
after a specified amount of time returns a response with a HTTP 408 Request Timeout instead.There is still work to be done, notably ensuring all 'old' API's are deprecated. I think I did most but probably there are some gaps left.
One notable issue is the inconsistency with the request API, eg.
.Content()
and.JsonContent()
whereas this new response API uses.Body()
and.JsonBody()
respectively (still doubting whether or not to just go with.Json()
. So probably have to align those too. The downside is more of the API surface changes, making refactoring/adoption harder.Alpha packages (from this PR) can be fetched from this repo its NuGet feed for testing (it is not published to NuGet until merged):
https://ci.appveyor.com/nuget/mockhttp/packages