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
Modifying the FirebaseMessaingClient.SendAsync and adding new Version(2, 0) should allow HTTP/2 to be used.
...
var request = new HttpRequestMessage()
{
Version = new Version(2, 0),
Method = HttpMethod.Post,
RequestUri = new Uri(this.sendUrl),
Content = NewtonsoftJsonSerializer.Instance.CreateJsonHttpContent(body),
};
Users of this library would probably also want to configure the EnableMultipleHttp2Connections property, but as far as I can gather this requires changes in the Google.Apis.Core and requires >= .NET 5
The text was updated successfully, but these errors were encountered:
@lahirumaramba Any news on this?
Because of the deprecation of the FCM batch API endpoint (in 15 days from now) and the HTTP V1 API relying mostly on HTTP/2 multiplexing to achieve greater throughput, this seems like a pretty important thing to look into.
Modifying the
FirebaseMessaingClient.SendAsync
and adding new Version(2, 0) should allow HTTP/2 to be used.Users of this library would probably also want to configure the EnableMultipleHttp2Connections property, but as far as I can gather this requires changes in the Google.Apis.Core and requires >= .NET 5
The text was updated successfully, but these errors were encountered: