Re: How to add more transports/protocols to XProc?

Personally I wouldn't want to have to state "these pipelines can execute in
parallel". As a programmer I want to focus on what are the logical
dependencies between my pipelines, and any given pipeline processor can work
out for itself whether or not it can execute them in parallel.

*I agree with your statements the only thought that comes to mind is when a
new developer comes on board in a company with pipelines that are say 50%
extension functions and he has no idea which ones are running in parallel
and well I don't know,, would it be obvious what was happening or be
documentation dependent?*


*<**p:parallel> perhaps like a p:group but tells you something relevant
about the relationship between two steps or is the lack of specification of
a port or the specification of a port easier? Dumb idea?



 (What is the emoticon for a positive non-rhetorical questions ;)??
***