 - In programming, message queueing is a method by which process (or program instances) can exchange or pass data using an interface to a system-managed queue of messages. Messages can vary in length and be assigned different types or usages. A message queue can be created by one process and used by multiple processes that read and/or write messages to the queue. For example, a server process can read and write messages from and to a message queue created for client processes. The message type can be used to associate a message with a particular client process even though all messages are on the same queue.
The message queue is managed by the operating system (or kernel). Application programs (or their processes) create message queues and send and receive messages using an application program interface (API). In Unix systems, the C programming language msgget function is used with various parameters specifying the action requested, message queue ID, message type, and so forth.
The maximum size of a message in a queue is limited by the operating system and is typically 8,192 bytes.
Other forms of interprocess communication (interprocess communication) include
semaphore, sockets, and shared memory.
 |
Learn more about Web services development |
| Operating system virtualization and Web services: Web services development and operating systems virtualization may be two different types of abstraction, but virtualization techniques look like they can have positive impact. |
| Creating rich Web service clients with Flash and Flex: Flash and Flex, titans within the RIA universe, now have XML, Ajax and scripting language functionality that make them better suited for Web services development. |
| Oracle links SOA, data services, BI and BAM: When it comes to incorporating data services, business intelligence (BI), and business activity monitoring (BAM), Oracle has not lost sight of its database roots. |
| Is Ruby on Rails ready for enterprise SOA?: Ruby on Rails promises ease in RESTful SOA development, but for it to move up to enterprise class, developers need to know how to make it scalable. |
| 2006 JavaOne coverage: A compilation of stories written about the JavaOne conference held in San Francisco this past May. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Chapter of the week: Working with Beehive Web services and JSR 181: This chapter, excerpted from Pro Apache Beehive, explores the Web service capabilities that are a part of Apache Beehive. You'll learn about JSR 181, Web Services Metadata for the Java ... |
| Chapter of the week: Introduction to Web services technologies: This chapter, excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, focuses on the standards that make up the Web services platform and how Web ... |
| LAST UPDATED: |
27 Jul 2001
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
Show me everything on 
