Topology Configurable Requester

[bieri]

The current requester does not expose the ability to configure its topologies

        public void Start()
        {
            subscription = bus.Subscribe<TResponse>(
                DispatchToRegisteredResponseHandler,
                    b => b.SetTopology<DefaultRequestTopologyBuilder>()
                          .DeliverUsing<TaskDeliveryStrategy>());

            var queue = subscription.Queues.First();
            publisher = bus.CreatePublisher<TRequest>(p => p.ReplyTo(queue.Name));
        }

@jonnii suggestions before I start hacking on this?

[jonnii]

maybe don't use request/response for your use case? I'm ok with a change that would support this as it's an obvious feature, but this would lead me to ask the question "what are you trying to do" as a request/response path which doesn't follow a "default-ish" topology is probably an accident waiting to happen.

[bieri]

the use case is certainly request response, the "custom topology" is to support a naming convention that is already in place elsewhere.

[jonnii]

let's do it.

[bieri]

@jonnii if you have a way you want it done let me know. I'm going to start working on this next week.

[bieri]

it does follow a default path, there is just a naming convention that is
followed, and i cant plug the names is all.

On Tue, Apr 5, 2016 at 2:25 PM, Jonathan Goldman notifications@github.com
wrote:

maybe don't use request/response for your use case? I'm ok with a change
that would support this as it's an obvious feature, but this would lead me
to ask the question "what are you trying to do" as a request/response path
which doesn't follow a "default-ish" topology is probably an accident
waiting to happen.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#78 (comment)

[jonnii]

try to follow the conventions as best as you can, we'll iterate from there.