Content deleted Content added
m v2.02 - Fixing innerlinks / WP:WCW project (Link equal to linktext) |
Scatterjoel (talk | contribs) Added use scenarios for asynchronous methods. |
||
Line 15:
}}</ref> is a set of [[web development]] techniques utilizing many web technologies used on the [[client-side]] to create asynchronous I/O [[Web application]]s.
* '''Asynchronous method dispatch''' (AMD), a data communication method used when there is a need for the server side to handle a large number of long lasting client requests.<ref>[https://web.archive.org/web/20130721031512/http://zeroc.com/doc/Ice-3.3.0/manual/Overview.3.2.html ICE usage of AMD].</ref> Using synchronous method dispatch (SMD), this scenario may turn the server into an unavailable busy state resulting in a connection failure response caused by a [[Computer network|network]] connection request [[Timeout (computing)|timeout]]. The servicing of a client request is immediately dispatched to an available [[thread (computer science)|thread]] from a [[Thread pool pattern|pool of threads]] and the client is put in a blocking state. Upon the completion of the task, the server is notified by a callback. The server unblocks the client and transmits the response back to the client. In case of thread starvation, clients are blocked waiting for threads to become available.
==Scenarios for Async==
1. '''I/O operations''': I/O operations like file I/O, network I/O, database I/O, (which is generally just network I/O), and web service calls benefit from asynchrony. Anytime that your code is making a database call, or a web service call or a network call or talking to the file system, that can be done asynchronously while that operation is in progress.
2. '''Performing multiple operations parallelly''': When you need to do different operations in parallel, for example, making a database call, web service call and any calculations, then we can use asynchrony.
3. '''Long-running event-driven requests:''' This is the idea where you have a request that comes in, and the request goes to sleep for some time waiting for some other event to take place when that event takes place, you want the request to continue and then send a response to client. So in this case, when request comes in, then thread is assigned to that request and as request goes to sleep, then thread is sent back to threadpool and as the task completes, then it generates the event and picks a thread from thread pool for sending response (the thread sent and picked from thread pool might or might not be the same.<ref>{{Cite web|url=https://www.codeproject.com/Tips/866962/Async-and-Await-Tutorial|title=Async and Await Tutorial|last=Goel|first=Gaurav|date=|website=Code Project|url-status=live|archive-url=|archive-date=|access-date=March 3, 2020}}</ref>
==See also==
| |||