c# - Is it advisable to call a WCF MSMQ Queued endpoint from a WPF client? -

c# - Is it advisable to call a WCF MSMQ Queued endpoint from a WPF client? -

i have messages want send multiple wpf client applications service can processed time after beingness sent. because of expected intermittent connectivity issues between client , server , necessary downwards time service, i'm inclined create wcf service queued endpoint. has worked me in past when client machines other servers , few in number. i'm concerned doing many client machines because think hard monitor many outgoing queues confirm no traffic beingness trapped on client machines. has tried doing before? if so, recommend it? why or why not? if haven't done it, can think of other pitfalls beside operational issue of monitoring outbound queues?

your question may improve worded as:

should scheme rolled out many nodes using msmq?

if essence of messaging , such systems designed irrespective of whether jms, apache mq, websphere, sonicmq, or msmq.

also, "traffic beingness trapped on client machines" - how define trapped? remember, application may quite happy message sitting locally days before beingness forwarded remote host. messaging systems have timeouts both reaching destination , destination process it.

i think fine.

c# wpf wcf architecture msmq