-
- Downloads
feat: allow single request scheduling
Until now the steering API client was expected to submit two requests. 1. The initial schedule request, with a `schedule` object 2. A second schedule request, with an additional `solutions` object This `solutions` object was empty, if no conflicts arose from the submitted schedule in the first place. But instead of just creating the requested schedule if no conflicts were detected we still required that second round-trip, introducing possible race conditions in the client, if another successful scheduling request was made between requests. From now on the steering API will create schedules if no conflicts have been detected and will only require the client to submit solutions if there really are conflicts to solve.
parent
51be0fbe
No related branches found
No related tags found
Please register or sign in to comment