News for hackers. Stuff that matters.
Re:The patented IBM multi-pipe: the evolution of Unix pipes by andyl on Friday March 15, 2013 @11:06AM (#5380975)
We need a generic pipe for internet services. Yes there is IFTTT and open-source clones, but they are not generically useful like the unix pipe on the command line.
Re:The patented IBM multi-pipe: the evolution of Unix pipes by hucker on Friday March 15, 2013 @11:14AM (#5381011)

    curl http://example.com/some/api/resource/json | sort | uniq | whatever?
Re:The patented IBM multi-pipe: the evolution of Unix pipes by tingletech on Friday March 15, 2013 @12:18PM (#5381347)
what good is it going to do to sort JSON? You need something like http://stedolan.github.com/jq/
Re:The patented IBM multi-pipe: the evolution of Unix pipes by andyl on Friday March 15, 2013 @12:46PM (#5381488)
jq - great tip - thanks for that!
Re:The patented IBM multi-pipe: the evolution of Unix pipes by hhw on Friday March 15, 2013 @02:06PM (#5382015)
tcputils from Debian does precisely that, allowing you to extend a UNIX pipe over a TCP connection. It's not generally available as a package in other distros, but you can easily grab the source from Debian and compile it yourself.

Consequently, tarballing to stdout and piping over tcputils is by far the fastest and most efficient way to send a large number of files over a network.

Re:The patented IBM multi-pipe: the evolution of Unix pipes by nathan7 on Friday March 15, 2013 @03:12PM (#5382364)
Bash actually supports /dev/tcp/HOSTNAME/PORT for this kind of thing. Ironically, that's disabled in the Debian bash package.
Re:The patented IBM multi-pipe: the evolution of Unix pipes by beachstartup on Friday March 15, 2013 @01:10PM (#5381627)
netcat comes pretty close...