Thanks for the reply!!
This may be more of “Itinerary/routing slip” design pattern type of a query ..just to understand the overall concept of Itinerary.
Iv’e understood the concept that the Itinerary pattern is used to decouple and allow the message to be routed across services by simply altering the items in the Itinerary.
So instead of going from A–>B–>C
I introduce another step and say it should go from A–>D–>B–>C
Now if this Itinerary pattern is to be succesfull ideally I should just modify the “Itinerary” and rest should be automatically handled.
As explained above if the “services are set to execute in the same location” or in the dispatcher pipeline one after the other how does the Itinerary pattern work ?
If the code (either in the receive/send handler or the dispatcher pipeline) was set to execute A–>B–>C and If I introduced another step “D” ; will it handle this change ? will I have to go and modify this if I alter the Itinerary ?
Assuming “B” was a WCF (SOAP) type of a call and now “D” is an Http post how does the code know how to handle the call made after “A”
If I have to go and alter the code related to “A” to make it understand that it has to go to D instead of B then whats the purpose of an Itinerary ?
Its like “hard coding” the logic into the service/container to allow it to route/call the next step in the chain…