Java message service
This book is a thorough introduction to Java Message Service (JMS), the standard Java application program interface (API) from Sun Microsystems that supports the formal communication known as ""messaging"" between computers in a network. JMS provides a common interface to standa...
| Autor principal: | |
|---|---|
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, California :
O'Reilly
2001.
|
| Edición: | 1st edition |
| Colección: | The Java series
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627328106719 |
Tabla de Contenidos:
- Java Message Service; Preface; Who Should Read This Book?; Organization; Software and Versions; Conventions; Comments and Questions; Acknowledgments; 1. Understanding the Messaging Paradigm; 1.1.2. Decentralized Architectures; 1.1.3. Hybrid Architectures; 1.1.4. Centralized Architecture as a Model; 1.2. The Java Message Service ( JMS); 1.2.1.2. Point-to-point; 1.3. Application Scenarios; 1.3.2. Business-to-Business; 1.3.3. Geographic Dispersion; 1.3.4. Building Dynamic Systems with Messaging and JMS; 1.4. RPC Versus Asynchronous Messaging; 1.4.2. Enterprise Messaging
- 2. Developing a Simple Example2.1.2. Examining the Source Code; 2.1.2.2. Obtaining a JNDI connection; 2.1.2.3. The TopicConnectionFactory; 2.1.2.4. The TopicConnection; 2.1.2.5. The TopicSession; 2.1.2.6. The Topic; 2.1.2.7. The TopicPublisher; 2.1.2.8. The TopicSubscriber; 2.1.2.9. The Message; 2.1.3. Sessions and Threading; 3. Anatomy of a JMS Message; 3.1.1.2. JMSDeliveryMode; 3.1.1.3. JMSMessageID; 3.1.1.4. JMSTimestamp; 3.1.1.5. JMSExpiration; 3.1.1.6. JMSRedelivered; 3.1.1.7. JMSPriority; 3.1.2. Developer-Assigned Headers; 3.1.2.2. JMSCorrelationID; 3.1.2.3. JMSType; 3.2. Properties
- 3.2.2. JMS-Defined Properties3.2.3. Provider-Specific Properties; 3.3. Message Selectors; 3.4. Message Types; 3.4.2. TextMessage; 3.4.3. ObjectMessage; 3.4.4. BytesMessage; 3.4.5. StreamMessage; 3.4.6. MapMessage; 3.4.7. Read-Only Messages; 3.4.8. Client-Acknowledged Messages; 3.4.9. Interoperability and Portability of Messages; 4. Publish-and-Subscribe Messaging; 4.1.2. The B2B Source Code; 4.1.2.2. The Retailer class; 4.2. Temporary Topics; 4.3. Durable Subscriptions; 4.4. Publishing the Message Persistently; 4.5. JMSCorrelationID; 4.6. Request and Reply; 4.6.2. TopicRequestor
- 4.7. Unsubscribing5. Point-to-Point Messaging; 5.2. The QWholesaler and QRetailer; 5.2.2. The QWholesaler Class; 5.3. Creating a Queue Dynamically; 5.4. Load Balancing Using Multiple QueueSessions; 5.5. Examining a Queue; 6. Guaranteed Messaging, Transactions, Acknowledgments, and Failures; 6.1.2. Store-and-Forward Messaging; 6.1.3. Message Acknowledgments and Failure Conditions; 6.2. Message Acknowledgments; 6.2.1.2. The server&s perspective; 6.2.1.3. The consumer&s perspective; 6.2.1.4. Message redelivery; 6.2.1.5. Point-to-point queues; 6.2.2. DUPS_OK_ACKNOWLEDGE; 6.2.3. CLIENT_ACKNOWLEDGE
- 6.3. Message Groups and Acknowledgment6.3.2. Message Groups in QRetailer; 6.4. Transacted Messages; 6.4.2. The Transacted Retailer Example; 6.4.3. Distributed Transactions; 6.5. Lost Connections; 6.6. Dead Message Queues; 7. Deployment Considerations; 7.1.2. Testing the Real-World Scenario; 7.1.2.2. Send rate versus receive rate; 7.1.2.3. Determining hardware requirements; 7.1.2.4. Finding or building a test bed; 7.1.2.5. Long duration reliability; 7.1.2.6. Memory leaks; 7.2. To Multicast or Not to Multicast; 7.2.2. UDP; 7.2.3. IP Multicast; 7.2.4. Messaging Over IP Multicast
- 7.2.4.2. Centralized and decentralized architectures
