WCF/MSMQ/可靠性 [英] WCF / MSMQ / Reliability

查看:103
本文介绍了WCF/MSMQ/可靠性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Juval Lowy的WCF书建议使用持久性队列(通过MSMQ)传输的消息将始终到达.

这是由于排队的消息保存在磁盘中,因此即使关闭计算机也可以幸免.

我的客户端应用程序对已调度消息的唯一担心是它们到达主机.

在了解这一点之前,我正在设计计时器,确认请求并做出响应,所有这些都会增加机器负载和网络流量,而在这种环境中,出于性能方面的考虑,必须将两者均保持在最低水平.

我可以有效地解雇"这一想法,因为他知道消息将始终被传递.

Juval Lowy''s WCF book suggests that messages transmitteed using persistent queues (via MSMQ) will always arrive.

This is due to the queued messages being held in disk so it will even survive a shutdown of the machine.

My client application''s only concern regarding dispatched messages is that they arrive at the host.

Before I learned this nugget, I was designing timers, acknowlegement requests and responeses all of which increase machine load and network traffic in an enviroment where both have to be kept to a minimum for performance reasons.

This notion that I can effectively ''fire and forget'' in the knowlege that the message will always be delivered is hugely attractive.

Is it too good to be true?

推荐答案

如果您可以将其作为有效的站位,我会感到惊讶,如果传输层出现故障,消息将未交付,它可能仍然存在,并且可能会自动重新发送,但重试次数有限.

我也认为异步回调是消息到达的令人满意的确认
I''d be astonished if you can take that as a valid stand, if the transport layer goes down the message will not be delivered, it may still exist and may automatically resend but for a limited number of retries.

I would also consider the asynch callback a satisfactory confirmation the message arrived


这篇关于WCF/MSMQ/可靠性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆