Basket (0)
Wishlist (0)
Your personal newsletter
__

Pro MSMQ

Microsoft Message Queue Programming
 
Edition number: Softcover reprint of the original 1st ed.
Publisher: Apress
Date of Publication:
Number of Volumes: 1 pieces, Book
 
Normal price:
Publisher's listprice:
EUR 53.49
Estimated price in HUF:
22 072 HUF (21 021 HUF + 5% VAT)
Why estimated?
 
Your price:
17 658 (16 817 HUF + 5% VAT )
discount is: 20% (approx 4 414 HUF off)
Discount is valid until: 30 June 2024
The discount is only available for 'Alert of Favourite Topics' newsletter recipients.
Click here to subscribe.
 
Availability:
Estimated delivery time: In stock at the publisher, but not at Prospero's office. Delivery time approx. 3-5 weeks.
Not in stock at Prospero.
Can't you provide more accurate information?
 
Add to basket
  Piece(s)

 
Long description:

This will be the only book on the market with in-depth coverage of using Message Queuing from .NET code ? it won't just be the number one in its category; it will be the only book in its category.


* The only book targeted at developers with in-depth coverage of MSMQ 3.0 and MSMQ triggers



* The only MSMQ book that covers working with the PocketPC


Covers VB, C++, and C

and will appeal to all developers using MSMQ, no matter what language they use

Highlights problems such as the lack of support for the System. Messaging namespace in the .NET Compact Framework and shows how to get around the problems



Message Queuing provides a way for applications to communicate asynchronously, and has often been compared to e-mail, but for applications rather than people. On Windows, Message Queuing is implemented in Microsoft Message Queuing, or MSMQ. A client application can communicate with a server by sending data in the form of an MSMQ message to a particular queue, where the server application can retrieve it and process it. Because the message will remain on the queue until it is retrieved, we can guarantee that it will be processed at some point, even if the server application is down when the message is sent.



In this book, we look at how we can use MSMQ to provide robust, asynchronous communication between our applications. MSMQ provides three APIs that we can use to incorporate message queuing into our applications ? a C API that we can use from unmanaged C/C++ code, a COM component that we can use from VB or C++ code, and the System.Messaging namespace, which provides a simple way to integrate MSMQ with managed C

and will appeal to all developers using MSMQ, no matter what language they use

Highlights problems such as the lack of support for the System. Messaging namespace in the .NET Compact Framework and shows how to get around the problems

Table of Contents:
NO APPLICATION IS AN ISLANDo o o In today's connected world, each and every professional developer must assume that his or her applications will need to communicate with other applications. Distributed applications, however, present a large set of unique challenges, like, what do I do when the network is disconnected? How do I coordinate the actions of two separate applications? How do I handle peak times? How do I guarantee delivery? How do I upgrade my application without breaking the communication? We at the Microsoft Message Queue (MSMQ) team have worked hardto provide an elegant solution to these questions and many others. This book will help you leverage this work by using MSMQ in your distributed applications so that you will be able to concentrate on the business logic rather than network problems. What is MSMQ? MSMQ is message-oriented middleware (MOM) that comes as a standard component ofWindows and allows applications to exchange messages among them using queues-outgoing queues for Iilessages waiting to be sent, and incoming queues for messages waiting to be received. Queues-like dams-guarantee nice and controlled flow of information, even when the network is congested or suffers frequent disconnects. Moreover, queues are a very natural programming metaphor. Most people would agree that working from a queue of to-do tasks is more effective than responding to requests on the spot. The same is true for computer programs. Programs that process queues of incoming messages tend to be simpler and more efficient than programs acting on interrupts.