Skypipe : a cloud based named pipe
klaig.blogspot.be
klaig.blogspot.be
cat /etc/issue.logo | skypipe gentoologo # no
skypipe gentoologo < /etc/issue.logo # yes
http://partmaps.org/era/unix/award.html#catIt looks like people forgot how to develop simple protocols for this sort of thing. A simple protocol for remote named pipes, a client and a server, and a wrapper/gateway for dotCloud/HTTP wouldn't take a (very) long time to develop, wouldn't be completely dependent on an external service, and would probably develop into something bigger --- even for anonymous file sharing!
I really would like to know why programmers, in general, seem not to be doing this sort of thing anymore. Sorry if it looks like some sort of misplaced criticism, I'm posing all of it genuinely as a question to the community.
But here, it makes the thing really easy, it autodeploys, the underpinning technology (0mq) makes the socket rendez-vous easy. For a first proof of concept I just love the usability !
Now yeah you can do it by installing a proxy on one of your servers ... ha but first you need a public server on the internet, tweak the services, expose it a little bit more to hacks etc etc ...
Easy to install (inetd/xinetd), easy to upgrade, self cleaning, nice behaviour when you reach the limit, the command line tool are autonomous (just put them in your PATH), the developper is (very) reactive. It just works.
It is as efficient as the website is old-school =) I'm an enthousiastic FEX administrator and user !
- "Skypipe : a cloud based named pipe" should be "Skypipe : a cloud-based named pipe"
- "... no IP to know, no tunnel to setup, nothing." should be "... no IP to know, no tunnel to set up, nothing."
- "then asks you and remember your credential for access" should be "then asks you and remember your credentials for access"