Please, consider http://gist.github.com/383784
(10:24:30 PM) Vladimir: deanlandolt pointed out the difference between start()/end() which is used to instruct the store backend to return partial data, and slice(), which just narrows the result set already fetched from the backend
(10:26:28 PM) Vladimir: we should always fetch totalCount, regardless of directives.start/end being specified, or the whole if(totalCountPromise){... branch is missed, leading to incorrect results
(10:27:29 PM) Vladimir: pintura should wait until responseValue promise fulfilled, or we never get totalCount and never report correct Content-Range:
(10:30:06 PM) Vladimir: pintura should not guess of how much data store.query() provides, it should just rely on metadata.start/end which, in turn, can be mangled by the store. That way the consistency keeps: when we set Range: items=1-2 for GET /Obj/?start(3)&end(6), the store reports obj[3:6] and not obj[1:2](10:30:25 PM) Vladimir: All these fixed in the gist
(10:30:26 PM) Vladimir: TIA
Please, consider http://gist.github.com/383784 (10:24:30 PM) Vladimir: deanlandolt pointed out the difference between start()/end() which is used to instruct the store backend to return partial data, and slice(), which just narrows the result set already fetched from the backend (10:26:28 PM) Vladimir: we should always fetch totalCount, regardless of directives.start/end being specified, or the whole if(totalCountPromise){... branch is missed, leading to incorrect results (10:27:29 PM) Vladimir: pintura should wait until responseValue promise fulfilled, or we never get totalCount and never report correct Content-Range: (10:30:06 PM) Vladimir: pintura should not guess of how much data store.query() provides, it should just rely on metadata.start/end which, in turn, can be mangled by the store. That way the consistency keeps: when we set Range: items=1-2 for GET /Obj/?start(3)&end(6), the store reports obj[3:6] and not obj[1:2](10:30:25 PM) Vladimir: All these fixed in the gist (10:30:26 PM) Vladimir: TIA