Recent Features
| |||||||||||||
Evolution of shells in Linux (developerWorks)Evolution of shells in Linux (developerWorks)Posted Dec 9, 2011 20:20 UTC (Fri) by ccchips (guest, #3222)In reply to: Evolution of shells in Linux (developerWorks) by Cyberax Parent article: Evolution of shells in Linux (developerWorks)
> PowerShell allows bidirectional communication while Unix pipes are traditionally unidirectional.
Can you give us some examples or links to some examples of this bidirectional communication and its advantages/disadvantages? Only thing I have found so far is that you can use a .net class to set up a named pipe.
(Log in to post comments)
Evolution of shells in Linux (developerWorks) Posted Dec 10, 2011 3:08 UTC (Sat) by Cyberax (✭ supporter ✭, #52523) [Link]
Bidirectional pipes are rarely used in PowerShell - it's a minor feature. More exactly, you can provide your own implementation for a pipe. Including pipes that use pigeon mail or encode data as smoke signals.
Evolution of shells in Linux (developerWorks) Posted Dec 16, 2011 3:56 UTC (Fri) by useerup (guest, #81854) [Link]
I believe he may be referring to the fact that PowerShell not only allows objects to be passed through the pipes, but also allows you/the script to actually *interact* with the objects, ie calling methods.
|
|||||||||||||