So now I am going to narrow the scope of the exchange I am working on to simply maintaining Airline Profiles Repository and Matching Engine (two separate projects). No need to passing through or proxy functions.
I still disagree with this.
now go and tell the OTA tech team...
implement this pattern
but consider this:
Alrline A uses SOAP, with this required headers and this specific authentications
Airline B uses plain HTTP, with HTTP basic Auth and this specific HTTP headers
and so on
you’ll see their face :)
One way to overcome this is simply to put adapters in front of these core two functions
this “adapters” would depend a lot on everyone’s case
but yes, the NDC SDK’s I was doing were intended to deal with this properly
well, at the end we had two weeks to work on it
not too much time to do all the abstraction I think it was required
Hey, @nderkach are you experiencing recently problems to access BA sandbox?
somthing like <Description>NDC_DIST_1005 - Unable to proceed as aggregator Travel is not recognised.</Description>