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
I have a question about your usage of httpx client. As I understand from FCM documentation, after upgrading to HTTPv1 API the recommended way to send batch messages is to use multiplexing via HTTP/2 protocol.
To use it with httpx you need to install httpx[http2] and pass http2 flag to client
httpx.AsyncClient(http2=True)
otherwise it establishes connection with HTTP1.1(now it works such way)
So, my question is it was a design choice not to use http2(for some reasons) or just missed?
The text was updated successfully, but these errors were encountered:
Regarding your question about the usage of the httpx client, at the time we started the project, HTTP/1.1 met our requirements and fit the plans we had in place. We did not initially incorporate HTTP/2, and we appreciate you bringing this to our attention.
We will certainly look into updating the implementation to utilize HTTP/2 as per the recommended approach for sending batch messages via the HTTPv1 API. Additionally, we always welcome contributions, so if you're interested in helping with this update or any other aspect of the project, it would be greatly appreciated.
Thanks for a great project
I have a question about your usage of httpx client. As I understand from FCM documentation, after upgrading to HTTPv1 API the recommended way to send batch messages is to use multiplexing via HTTP/2 protocol.
To use it with httpx you need to install httpx[http2] and pass
http2
flag to clientotherwise it establishes connection with HTTP1.1(now it works such way)
So, my question is it was a design choice not to use http2(for some reasons) or just missed?
The text was updated successfully, but these errors were encountered: