-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question About JsonSerializer.DeserializeAsyncEnumerable Behavior #56055
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsHi, I have a question around
And one which uses
The output from the first one is as follows.
Which confirms that ASP.NET Core is flushing the results as they come. The output from the second is as follows.
This suggest that I haven't found this explained in documentation, so my question would be if this is expected behavior or am I doing something wrong? The project where I'm plaining with this is available here.
|
Tagging subscribers to this area: @eiriktsarpalis, @layomia Issue DetailsHi, I have a question around
And one which uses
The output from the first one is as follows.
Which confirms that ASP.NET Core is flushing the results as they come. The output from the second is as follows.
This suggest that I haven't found this explained in documentation, so my question would be if this is expected behavior or am I doing something wrong? The project where I'm plaining with this is available here.
|
Hi @eiriktsarpalis , thank you for taking a look at this. My only two questions would be if there is a chance that fix is going to make it into Preview 7, and are there past previews which have the correct behavior? |
Once merged the fix would be committed to the RC1 branch and not Preview 7. I believe preview4 might not incorporate the regression although that release is no longer supported. |
Thank you! |
Hi,
I have a question around
JsonSerializer.DeserializeAsyncEnumerable
. I was experimenting with async streaming between ASP.NET Core and HttpClient in .NET 6. I have created two methods on the client side. One which outputs the raw data returned by the ASP.NET Core endpoint.And one which uses
JsonSerializer.DeserializeAsyncEnumerable
to deserialize the stream.The output from the first one is as follows.
Which confirms that ASP.NET Core is flushing the results as they come.
The output from the second is as follows.
This suggest that
JsonSerializer.DeserializeAsyncEnumerable
is waiting for the entire stream before it starts deserializing.I haven't found this explained in documentation, so my question would be if this is expected behavior or am I doing something wrong?
The project where I'm plaining with this is available here.
The text was updated successfully, but these errors were encountered: