Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Message queue
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Synchronous vs. asynchronous== <!-- WEIRD SECTION, SHOULD THIS NOT BE PUT INTO THE ASYNCHRONOUS ARTICLE SECTION SHOULD BE DELETED. DOES NOT ADD FACTS -->Many of the more widely known [[communications protocol]]s in use operate [[Synchronization (computer science)|synchronously]]. The HTTP protocol – used in the [[World Wide Web]] and in [[web service]]s – offers an obvious example where a user sends a request for a web page and then waits for a reply. However, scenarios exist in which synchronous behaviour is not appropriate. For example, [[AJAX]] ([[wikt:asynchronous|Asynchronous]] [[JavaScript]] and [[XML]]) can be used to asynchronously send text, JSON or XML messages to update part of a web page with more relevant information. [[Google]] uses this approach for their Google Suggest, a search feature which sends the user's partially typed queries to Google's servers and returns a list of possible full queries the user might be interested in the process of typing. This list is asynchronously updated as the user types. Other asynchronous examples exist in event notification systems and [[Publish–subscribe pattern|publish/subscribe]] systems. * An application may need to notify another that an event has occurred, but does not need to wait for a response. * In publish/subscribe systems, an application "publishes" information for any number of clients to read. In both of the above examples it would not make sense for the sender of the information to have to wait if, for example, one of the recipients had crashed. Applications need not be exclusively synchronous or asynchronous. An interactive application may need to respond to certain parts of a request immediately (such as telling a customer that a sales request has been accepted, and handling the promise to draw on inventory), but may queue other parts (such as completing calculation of billing, forwarding data to the central accounting system, and calling on all sorts of other services) to be done some time later. In all these sorts of situations, having a subsystem which performs message-queuing (or alternatively, a broadcast messaging system) can help improve the behavior of the overall system.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)