Durable Messages

[craiggwilson]

I'm new to mass transit, so let me describe what I have and what I
need and hopefully you can tell me how best to set it up. I have 2
different windows services running on 2 different boxes. One is the
gateway and the other is the processor.

1) The gateway is the communications service and when it receives a
datagram, it publishes a message indicating it's receipt along with
some other information. At this point, it is fire and forget. The
gateway never needs to know anything else about this message. This
works just fine.

2) The processor has subscribed to the message and processes it when
it gets received. This also works just fine.


BUT, I need to be able to take down the processor for upgrades while
leaving the gateway running. Currently, this also works because I
don't call unsubscribe() when the processor stops. Therefore, when
the processor starts up again, it gets all those receipt messages and
can process them.

My question is: is this the correct way of doing this? It seems dirty
to not call unsubscribe. Do sagas have a place here? I understand
them conceptually, but it seems like that the gateway would then care
about whether or not the receipt message was picked up.

Any ideas? thoughts? tips?

[Chris Patterson]

That's how it works, you just don't call Unsubscribe.

There may be a more explicit way to specify the subscription is "durable" at some point in the future, but it will likely do the same thing.

Chris Patterson

chrisfr...@gmail.com

[craiggwilson]

Ok, tremendous. Thanks for the help!!!

> chrisfromtu...@gmail.com