Multiple receivers in single process

[dziedrius]

I've wrote question about that in stackoverflow, but still haven't received clear answer (I'm offering bounty on it right now, also it is different case, why I would need several receivers in single process - http://stackoverflow.com/q/9411638/212121), so I'll try to describe situation and may be my approach is wrong in the first place.
So situation is this:
There is publisher, which generates events on product information change.

And then there are several external sales channels, where product updates must be pushed (let's say amazon.com, ebay.com).

Each channel is separate event subscriber, and all channels are in single process (although different threads, so they can run concurrently). So it turns out, that each channel needs own receiver, because if there would be single receiver and on event it would loop through channels and process event data, would be a problem if single channel fails - let's say amazon.com would not accept requests, ebay would not receive updates also.

To have all channels as separate processes also is not a solution, because we have double digit of them, management and deployment all as separate processes would be ... not very sweet.

[johnsimons]

The stackoverflow question has an accepted answer, should we close this question?