Unix Named Pipe in 100 seconds

If you are not doing bidirectional communication between process, you might want to use unix named pipe (fifo) instead of unix domain socket. It's really just like read and write on a regular files. We can even easily write to unix named pipe using x86 assembly.
Related videos:
• Unix Domain Socket in ...
• You might not need HTTP
• Unix Socket HTTP in 10...
Playlist:
• You might not need
#linux #javascript #100secondsofcode #webdevelopment #computerscience #nodejs #programming #software

[@Ptolemarch]

Hahaha. "Here's the simplest IPC I can think of, and here's some example code in assembly."

[@ANONAAAAAAAAA]

Files are cached in memories by OS and read/write operations usually don't require accessing storage devices unless fsync system call is issued.

[@teamredstudio7012]

very interesting! Thanks for sharing

[@AK-vx4dy]

Interesting take from practical side and pros, i would like to see some cons also ;)

[@EndOfFilee]

great content ! keep it up.

[@jumpsareop]

Nice.

[@vilijanac]

This reminded me of, when you ctrl-Z a process, then do a $ bg in the shell. To check the progress of the process you enter: tail -f /proc//fd/1

[@UliTroyo]

It’s that easy to use Unix pipes?? And here I am using a whole-ass server like a sucker.

[@cristhiamtovar9003]

Wow