--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/effa40ec-20a4-4f10-bd2c-e59a4b2105f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Either way works, which is why it is available using both a send or a publish. And yes the routing is the same.It's a matter of preference really. Some like explicit commands to be sent as commands, others prefer the dynamic routing of just using types. So your choice!__
Chris Patterson
The IBus provides both the Request and PublishRequest methods. AFAIK, the major difference is the the former requires an endpoint address to be provided (E.g. RabbitMQ host and queue names). The later does not need that info, however its docs state "Using Request with an address is highly recommended".--In this context:1) Does the PublishRequest use the same routing algorithm (e.g. exchange with the message's name when using RabbitMQ) used by Publish?2) Why is Request preferable to PublishRequest? Don't having to know the endpoint address seems a good thing, from a client perspective. For instance, any entity that wants to change the customer address just needs to know the ChangeCustomerAddress message type and not the processor logical address. Am I missing something here?ThanksPedro
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/719634b2-ee82-4fec-bd62-225d91104f2a%40googlegroups.com.