> is not like multiple lines of code in a server side .asp php or node
program
> it is more like "ask for this, and depending on the answer,
> ask for this" like a "request tree"
Actually, that _is_ like asp, php or node program :) As for php guys
approach is nearly native, sync program code runs inbetween DB requests.
As for node.js guys it also could be understood in native paradigm: think
couchapp functions are kinda middleware in request processing chain, and
each middleware function can determine next step.
Somehow like express.js maybe, but in express you call next(args) when in
CouchDB you just return {path:"...", body:"args"}. Also in node your
middleware can be async, but in CouchDB it should be sync.
ermouth
2015-11-26 5:11 GMT+03:00 Johs Ensby <j...@b2w.com>:
> Ermouth,
>
> > On 25. nov. 2015, at 18.18, ermouth <ermo...@gmail.com> wrote:
> > chunked response and reduce approach
>
>
> I think both modes are valuable, conceptually we end up with 3 modes of
> respons
> Technically it makes sense to describe as server response.
>
> I am trying to think of how we want to spin this to the new developers
>
> I would recommend that we name the feature as seen from the front-end
> developer
>
> - single request
> - chained request
> - progressive load
>
> The 3rd being a variant of chained request not accumulating but spitting
> output into the client for as long as it takes
>
> "Single reqest" is the normal thing, but what we see as one of the painful
> limitations of Couch
> "Chained request" is the new thing that is not like multiple lines of code
> in a server side .asp php or node program, it is more like "ask for this,
> and depending on the answer, ask for this" like a "rewuest tree"
> "Progressive load" is a super way to improve performance, it is writing
> for UX, "what the user needs right away is... then .... and eventually
> she/he will be looking for .. if a link in the first chucks has been
> clicked yet"
>
> johs
