interleaved support

[Christoph Dorn]

hdon: Wes-: interleaved support was never implemented so you can do
javascript|external command|javascript, but not external
command|javascript|external command

[6:28pm] cadorn: that would be real nice
[6:32pm] cadorn: Is command|javascript|external command planned?

Can we discuss this a bit more?

Christoph

[Donny Viszneki]

The current implementation of the shellalike module's functionality uses blocking i/o selecting on a single file descriptor at a time. A proper reactor / event loop is what is needed to overcome this limitation.

As I may have mentioned earlier, I do have an implementation of the Node API built on NSPR, but I haven't had time to work on it much lately.

[Wes Garland]

On 22 September 2011 14:58, Christoph Dorn <chri...@christophdorn.com> wrote:

Can we discuss this a bit more?

Basically, in a CAY pipeline, we have (A)(B)(C).  If A or B or C is a string, it is run as a shell command (external), if it is a function, we use the function (internal) to consume and yield.

It looks like right now, you can do internal->external and external->internal, but not internal->external->internal or external->internal->external.  (internal and external can each be multiple steps of the same type)

This is a flaw in the shellalike module, but not one we are going to have time to address any time soon.  OTOH, the external->internal->external case can probably be worked around by opening a second CAY pipeline in the terminating internal expression.

Wes

--
Wesley W. Garland
Director, Product Development
PageMail, Inc.
+1 613 542 2787 x 102