Async Streaming in ASP.NET Web API

re: Async Streaming in ASP.NET Web API

Srigopal Chitrapu — Thu, 27 Dec 2012 21:55:58 GMT

Nice Example, which i am looking for.

re: Async Streaming in ASP.NET Web API

Aliostad — Mon, 27 Feb 2012 23:37:12 GMT

Just reading the headline I assumed this is to do with HTTP chunked encoding and I was surprised that the client side of it is done since AFAIK IIS does not support chunked encoding from the client. Is that statement still true?

Also I am wondering, how would be define that in a response? Do I need to set a property to chunked encoding?

Also would these Task<T>s and Tasks use the default scheduler - hence suffocate the ThreadPool threads? And as such, should we set a higher value for Min and Max of ThreadPool threads?

Sorry this is already three questions? Thanks :)

re: Async Streaming in ASP.NET Web API

Radenko Zec — Sun, 26 Feb 2012 14:56:52 GMT

What do you mean by talks to backend ? For example what do you recommend if my action just read data from Sql Server database based on some passed parameters (simple select statement with where) and returns JSON result ? Is it smart to use tasks here or not ?

re: Async Streaming in ASP.NET Web API

Henrik F Nielsen — Sun, 26 Feb 2012 14:48:46 GMT

A good rule of thumb is whether the action does any I/O (e.g. reading or writing to the network). For example, if an action talks to a backend, performs some form of aggregation of other services, or reads data from the request, then using Tasks is a good idea.

If this is not the case then as a general rule not using tasks is fine. There are of course exceptions to this rule such as actions doing parallelizable data crunching like ray tracing but that is rare in my experience.

re: Async Streaming in ASP.NET Web API

Radenko Zec — Sun, 26 Feb 2012 10:41:27 GMT

Do you recommend using Tasks for every action in WebApi to improve scalability or just for long running actions ?

re: Async Streaming in ASP.NET Web API

Henrik F Nielsen — Sat, 25 Feb 2012 21:42:04 GMT

Thanks for asking -- I did mean HttpContent because it applies to both client and server side. HttpRequestMessage, HttpResponseMessage, HttpContent, etc. sit on both the client side (as part of HttpClient) and on the server side (as part of ASP.NET Web API). That is, the way you can do push on client side works identical on server side.

Hope this helps,

Henrik

re: Async Streaming in ASP.NET Web API

James Manning — Sat, 25 Feb 2012 17:17:01 GMT

Small typo? I'm assuming you meant HttpClient?

...

In the previous blog “Push and Pull Streams using HttpClient” we described how to use push and pull streams with **HttpContent**

...