You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of calling Project, Membership, Versions, LocalizationTypes,StateTypes as individual calls, with the same arguments, we should create 1 REST endpoint that returns all the information in one request.
In the multi-page, we could likely further combine to call it once for all media and subdivide accordingly.
The text was updated successfully, but these errors were encountered:
An approach that could be exciting is a daisy-chain endpoint which allows other endpoints to be called in sequence from the daisychain endpoint. This eliminates round-trip times and overheads associated with connection intialization on data that need not or can not be parallelized. Another use of this endpoint could be multiple-data multiple-operation (e.g. bulk sets where each row gets its own value)
Instead of calling Project, Membership, Versions, LocalizationTypes,StateTypes as individual calls, with the same arguments, we should create 1 REST endpoint that returns all the information in one request.
In the multi-page, we could likely further combine to call it once for all media and subdivide accordingly.
The text was updated successfully, but these errors were encountered: