Aaronontheweb on 1.4.14
Aaronontheweb on master
Bump Mongo2Go from 2.2.14 to 2.… Bump MongoDB.Driver from 2.11.4… Bump Microsoft.NET.Test.Sdk fro… and 4 more (compare)
Aaronontheweb on 1.4.14
Aaronontheweb on dev
Added v1.4.14 release notes (#1… (compare)
using (var client = new HttpClient())
{
var request = new HttpRequestMessage(msg.HttpMethod, msg.Uri);
client
.SendAsync(request)
.PipeTo(Self);
}
@mmisztal1980 you can create a custom response wrapper in SendAsync
continuation like:
using (var client = new HttpClient())
{
var request = new HttpRequestMessage(msg.HttpMethod, msg.Uri);
var start = DateTime.UtcNow;
client
.SendAsync(request)
.ContinueWith(task => !(task.IsCancelled || task.IsFaulted) ? new SuccessfulResponse(task.Result, start: start, stop: DateTime.UtcNow) : new FailedResponse(task.Result, start: start, stop: DateTime.UtcNow) ,
TaskContinuationOptions.AttachedToParent|TaskContinuationOptions.ExecuteSynchronously)
.PipeTo(Self);
}
Task continuation options are used here to not spawn separate tasks for one simple operation (creating message wrapper), we attach it to task running SendAsync instead.
dev
due to a merge conflict - asked you to do a rebase on dev a couple of weeks ago and never heard back