The Fine Print: Infolets posters grant Infolets an independent copyright on their postings, and retain their own copyright. Posters retain full responsibility for their postings.
( Reply )
|
Re: An Open Source Alternative to .NET and Jini
by Jim Flanagan on Wednesday October 04, @04:06PM
|
Piper is significantly richer than the traditional world of pipes.
And herin lies the rub. The reason for the power and flexibility of pipes is that the pipe itself is very simple. All you do is connect the standard output of one program to the standard input of another. One doesn't have to build a description of the interface.
A pipeline is spontaneous and ad hoc.
Granted, that adapters are often employed by interjecting "filters" between elements of the pipe. These are generally awk or sed scripts, but are "first class" elements of the pipeline as well.
|
[
Reply to this ]
|
Re: An Open Source Alternative to .NET and Jini
by Shibu on Monday July 16, @06:29AM
|
Can u please inform me whose product Piper is ?
|
[
Reply to this ]
|
The Fine Print: Infolets posters grant Infolets an independent copyright on their postings, and retain their own copyright. Posters retain full responsibility for their postings.
( Reply )
|
Cameron Laird and Kathryn Soraiz have pointed me to Piper. Piper has taken the Unix concept of pipes and is attempting to bring it to the Internet at large. Instead of the pipe symbol "|", Piper has developed a simple graphical representation of component relationships that users can easily manipulate. Piper uses simple lines and arrows to connect different components together and then allows users to change and add to these connections at will. Piper is significantly richer than the traditional world of pipes. The goal of Piper is to be a complete XML component language that allows users to construct any program they need from a set of components located anywhere on the Internet. Piper is still in the early stages of development, but it is a project that bears watching.