Re: Threading and ordering

Romain Deltour <rdeltour@gmail.com> writes:
> That said, this is not a *strict* dependence, we could certainly find
> a workaround if the XProc spec was to change. Another option would be
> to keep the default behavior and add an option to explicitly declare
> when the order doesn't matter, e.g. using an extra attribute on the
> p:input and p:output ?

Yes, that's about where I've come to in thinking about it. If the
order matters, some (in the worst case, all but one) documents will
have to be buffered so that they can be delivered in the right order.

Giving pipeline authors a way to indicate that order doesn't matter
will potentially make some pipelines consume less memory and run
faster.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 512 761 6676
www.marklogic.com