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-oriented middleware
(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!
==Trends== * [[Advanced Message Queuing Protocol]] (AMQP) provides an open standard application layer protocol for message-oriented middleware.<ref>OASIS AMQP version 1.0, sections 2.6.7-2.6.8". OASIS AMQP Technical Committee. Retrieved 18 June 2012.</ref> * The [[Object Management Group]]'s [[Data Distribution Service]] (DDS) has added many new standards to the basic DDS specification. See [https://web.archive.org/web/20130202055113/http://www.omg.org/technology/documents/dds_spec_catalog.htm Catalog of OMG Data Distribution Service (DDS) Specifications] for more details. * The [[Object Management Group]]'s [[Common Object Request Broker Architecture]] (CORBA) has added many new standards recently including a new language mapping to [[C#]] and an update to the IDL to C++ mapping specification to support the latest updates to the [[C++]] language standards. See [https://www.omg.org/spec/category/corba-platform Catalog of OMG CORBA Specifications] for more details. * [[Extensible Messaging and Presence Protocol]] (XMPP) is a communications protocol for message-oriented middleware based on Extensible Markup Language (XML).<ref>Johansson, Leif (April 18, 2005). "XMPP as MOM". Greater NOrdic MIddleware Symposium (GNOMIS). Oslo: University of Stockholm</ref> * [[Streaming Text Oriented Messaging Protocol]] (STOMP), formerly named TTMP, is a simple text-based protocol, provides an interoperable wire format that allows STOMP clients to talk with any Message Broker supporting the protocol.<ref>{{Cite web|url=https://stomp.github.io/stomp-specification-1.2.html |title=STOMP Protocol Specification, Version 1.2 |date=22 October 2012 |website=stomp.github.io}}</ref> * An added trend sees message-oriented middleware functions being implemented in hardware, usually in a [[field-programmable gate array]] (FPGA), [[application-specific integrated circuit]] (ASIC), or other specialized silicon chip.<ref>[http://advice.cio.com/ralph_frankel/are_you_soft_in_the_middle_the_future_of_enterprise_it_rests_in_hardware_applications?commentpage=1 Are You Soft in the Middle? The future of enterprise IT rests in hardware applications] {{webarchive|url=https://web.archive.org/web/20090209044943/http://advice.cio.com/ralph_frankel/are_you_soft_in_the_middle_the_future_of_enterprise_it_rests_in_hardware_applications?commentpage=1 |date=2009-02-09}}</ref> <ref> [https://www.ois.com/index.php/orbexpress-fpga/ ORB''express'' for Field Programmable on Gate Arrays] ([[FPGA]])</ref>
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)