Ok... Now I understand. :)
On 5/3/13 11:13 AM, "Rob van der Heij" <[email protected]> wrote: > Sure, the "testing" is not valid so gets rc-3 and seems to stop the pipe. > Try ID or L > I understand there is a reason a real application takes 2 months more :-) > On May 3, 2013 5:37 PM, "Nix, Robert P." <[email protected]> wrote: > >> On my system, it breaks... >> >> The first problem is a typo, I think: "i :faninany" should be "i: >> faninany". >> After fixing that, I get: >> >> pipe (end ?) tcplisten 4231 | take| i: faninany | tcpdata sf | cms | >> reverse >> | elastic | i: ? cons asynch | reverse | tcpclient >> 127.0.0.1 4231 sf | cons >> Testing >> FPLTCQ1015E ERRNO 54: ECONNRESET >> FPLMSG003I ... Issued from stage 3 of pipeline 2 >> FPLMSG001I ... Running "tcpclient 127.0.0.1 4231 sf" >> Ready(-0003); T=0.01/0.01 10:35:07 >> >> -- >> Robert P. Nix Mayo Foundation .~. >> RO-OC-1-18 200 First Street SW /V\ >> 507-284-0844 Rochester, MN 55905 /( )\ >> ----- ^^-^^ >> "In theory, theory and practice are the same, but >> in practice, theory and practice are different." >> >> >> >> On 5/3/13 4:41 AM, "Rob van der Heij" <[email protected]> wrote: >> >>> On 3 May 2013 11:16, FAULHABER Michael >>> <[email protected]>wrote: >>> >>>> >>>> So if you look at the description of the TCP.. stages, they are not >>>> written for beginners, some options are not detailed as for other >> stages, >>>> you must already have some knowledge about TPC/IP. >>> >>> >>> I beg to differ... I know very little about TCP/IP and can't even spell >>> socket, but with CMS Pipelines support I could write a TCP/IP client and >>> server in a few minutes. In fact, both of them sitting on the *same* CMS >>> command line when you take out the blanks :-) Since it's Friday, I >> leave >>> it to the follow plumbers to see what it does... >>> >>> pipe (end \) tcplisten 4231 | take| i :faninany | tcpdata sf | cms | >>> reverse | elastic | i: >>> \ cons asynch | reverse | tcpclient 127.0.0.1 4231 sf | >> cons >>> >>> | Sir Rob the Plumber >>
