Tag Info

New answers tagged

2

ASP.Net that does not use the Task Parallel Library (TPL) is limited in the number of requests it can handle concurrently by the number of threads in a thread pool. ASP.Net that uses the TPL is limited by the CPU/memory/IO of the machine handling requests. The Task Parallel Library (TPL) does not consume threads in the way you seem to think it does. Tasks ...


3

Since no one else has answered and I've now had a full day to remember all my old comp sci courses, I'll try writing a proper answer this time. To the best of my knowledge, all asynchronous behavior in computers is at some level implemented by putting things in a queue and coming back to that queue later to process the things when it's more convenient. When ...


0

Non-blocking reads can be especially useful in contexts where data may or may not arrive, but if data does arrive it should affect the behavior of an action being performed. For example, if an interactive program that communicates via TCP expects to perform some computations in response to a request, but it's possible that the client might discover--before ...


2

The main reason async read is handy if you still have other work to do or more often because there is another input source you also need to listen to. For example a GUI you need to listen to the user input besides getting the image from the disk. Without asynchronous IO you would need to start a new thread every time you start to read something with a ...



Top 50 recent answers are included