Content deleted Content added
m →References: Per the WP:STUBSPACING guideline |
Fits better, it's a short article |
||
Line 5:
A common way for dealing with asynchrony in a [[application programming interface|programming interface]] is to provide [[subroutine]]s (methods, functions) that return to their caller an object, sometimes called a [[futures and promises|future or promise]], that represents the ongoing events. Such an object will then typically come with a synchronizing operation that blocks until the operation is completed. Some programming languages, such as [[Cilk]], have special syntax for expressing an asynchronous procedure call.<ref name="spp">{{cite book |first1=Michael |last1=McCool |first2=James |last2=Reinders |first3=Arch |last3=Robison |title=Structured Parallel Programming: Patterns for Efficient Computation |publisher=Elsevier |year=2013 |pages=30}}</ref>
Examples of asynchrony include the following:
* "[[Ajax (programming)|Ajax]]", short for "asynchronous [[JavaScript]] and [[XML]]")<ref>{{cite web|url=http://shiflett.org/blog/2007/apr/ajax-is-not-an-acronym|title=Ajax Is Not an Acronym|author=Chris Shiflett|publisher=}}</ref><ref>{{cite web|url=https://blogs.oracle.com/arungupta/entry/ajax_vs_ajax_ajax_ofcourse|title=AJAX vs Ajax - Ajax ofcourse! (Arun Gupta, Miles to go ...)|publisher=}}</ref><ref name="garrett">{{cite web
| url=http://www.adaptivepath.com/ideas/essays/archives/000385.php
| |||