CPC G06Q 10/02 (2013.01) [G06Q 10/025 (2013.01); G06Q 30/0222 (2013.01); G06Q 30/0623 (2013.01); G06Q 50/12 (2013.01); G06Q 50/14 (2013.01); G06F 16/951 (2019.01)] | 23 Claims |
1. A method performed by a split vacation deal generating server including at least one processor, the method comprising:
i. storing at least one response, received via at least one API from at least one specific data supplier server, as a record in a cache, the record including a cost, a time period to which the cost applies, and an ID of the specific data supplier server, and incrementing monitoring data quantifying at least a specific parameter currently characterizing the at least one data supplier server's interaction with the split vacation deal server;
ii. after sending at least one individual batch from among plural batches of queries each including at least one query:
terminating sending of batches if a predetermined logical combination of at least the following two stopping criteria a, b, computed by said processor, is met:
a. at least one stopping criterion (aka “saves enough” stopping criterion) is met by at least one individual numerical value of at least one individual response from among responses received to said queries, because said at least one individual numerical value saves enough, compared to at least one default numerical value, according to said “saves enough” stopping criterion; and
b. at least one stored “avoid data supplier policy-defined limit” stopping criterion reflecting at least one limit defined by a policy for at least one specific aspect of the at least one data supplier server's interaction with the split vacation deal server has been reached by monitoring data quantifying at least said specific parameter currently characterizing the at least one data supplier server's interaction with the split vacation deal server.
|