Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Dody Gunawinata
    @dodyg
    Is this design for the data generator or to hold the actual data of the PSS sandbox?
    Jorge Díaz
    @xurde
    @dodyg well, the “PSS-ish” Sandbox actually will generate the data
    at least that’s my point of view
    Dody Gunawinata
    @dodyg
    So it's probably good to have a log message table so the devs knows what's going on
    Jorge Díaz
    @xurde
    log message table?
    like a changelog?
    the data fixtures will be easily editable for each case
    in case you want to have more “realistic” data or more fakeish
    that’s the point of having data fixtures
    it’s just YAML files easy to edit
    Roman Kalyakin
    @theorm
    Data model looks sensible. It obviously misses some fields, but that’s fine - it can be added as more fixtures are added and there is better understanding of how it should be organised.
    Jorge Díaz
    @xurde
    yes, it’s just a very early-stage one. Once you see how migrations/fixtures work I hope you can help a bit on tunning up this things
    Roman Kalyakin
    @theorm
    Yeah, fixtures are easy to deal with in Ruby.
    Nikolay Derkach
    @nderkach
    Finally after weeks of back and forth with BA support, I was able to create my first order in their NDC sandbox. Spoiler alert: all the examples on Mashery are completely broken. Turned out that the agency id which was assigned to me was Swiss, and therefore I could only charge my customers in CHF, whereas all their examples contained GBP. After you call Shopping, you need to request FlightPriceService (the price might be different). Also, when you create an order, you need to provide credit card details including surcharge, which is 0 as I was told for all non-UK agents.
    Also I wonder if their sandbox works with the same PSS as their production environement, it took about 15 seconds to create an order.
    Nikolay Derkach
    @nderkach
    Here are example schemas for ba.com sandbox which actually work: https://github.com/nderkach/ba-ndc-examples
    Jorge Díaz
    @xurde
    @nderkach This great to know
    15 secs to create an order!!
    I hope the airlines learn a bit about the API Economy before launching NDC gateways in production :(
    otherwise, i will become hardly usable
    and the issue about the currencies is just CRAZY
    BTW, @nderkach you have to test Postman
    I don’t think you use curl again… :)
    Roman Kalyakin
    @theorm
    Postman is good. But for sharing requests in documentation curl is still the way to go.
    Jorge Díaz
    @xurde
    not sure if you tried shared postman collections.
    but agree that for docs is like the standard way.
    Roman Kalyakin
    @theorm
    I could not find a nice way to share them in a markdown file, but I haven’t looked into it a lot.
    Nikolay Derkach
    @nderkach
    I think the main limitation here is their PSS, there must be a lot of legacy software in there. I was told that the booking process in the sandbox is identical to production, including calling out to the external reservation engine. They also claim that the end-to-end response time would be about 10 sec end-to-end in production.
    Nikolay Derkach
    @nderkach
    @xurde I had been using Postman for a little while, with a Chrome plugin. I mostly used it to consume APIs, but also for reverse-engineering. I recall one time it drove me absolutely insane, and I was getting a different response with the headers which had to work as is. Turned out Postman was adding some headers/cookies which fucked up everything. From that moment on, I decided to go old-school, at least with curl I have a better control of what is going on. Also, if I need to reverse engineer a website for example, I could just use Chrome’s Network Monitor and “copy as curl” is extermely convenient to tinker with request contents. And finally, as @theorm mentioned: it’s great for documentation.
    Jorge Díaz
    @xurde
    Ok, it’s weird it sends anything hidden
    normally it’s pretty clear with that
    take a look at the latest version, still a Chrome App but not a plugin anymore
    also, they added a whole colaborative suite
    but again, I’m totally ok to use curl for the documentation, actually I think it’s the way to do it
    Dody Gunawinata
    @dodyg
    Jorge Díaz
    @xurde
    humm.. any particular page on its 116? xD
    or just as a whole it
    Dody Gunawinata
    @dodyg
    No idea.
    I asked the following question two weeks ago to the NDC people : "Is there any reason why an NDC aggregator should relay messages between OTA and Airline beyond AirShoppingRQ/Rs? "

    This is the answers:

    This point is actually covered in the NDC Implementation Guide V2 that was just published.

    Indeed, the aggregation function is useful during the initial phase of the shopping conversation – so that the seller/agent can reach out to several airlines in parallel via an aggregator. (see page 14 – An Aggregator’s role is to request Offers from Airlines based on a shopping request initiated by a Seller, and respond to the Seller with a consolidated set of these Offers. This consolidation could involve receiving one or more Offers from Airlines and deciding which Offers and in what form they should be presented to the Seller).

    Later on (see page 17), If a Customer chooses to accept an Offer, the Seller will ask the Airline to create an Order. This Order creation request may be sent directly to the Airline, or it may still pass through the Aggregator. If the request passes through the Aggregator, their role is passive and they will act as a proxy, they may continue to aid with authentication of the messages/the actors involved, but they will no longer be applying any routing logic as the Order is placed with the specific Airline that created the chosen Offer originally.

    Dody Gunawinata
    @dodyg
    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.
    Jorge Díaz
    @xurde
    I still disagree with this.
    I mean
    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
    Airline C….
    and so on