David J. Paola

HTTP as a file system

I want to be able to treat URIs as files in unix:

$ cat /http/someblog.com/post/48

There are all sorts of implications here. In Unix, you can read and write files. You can also execute files:

$ /http/some_music_site my_mp3_file.mp3

Arguments could be passed as byte streams or whatever is simplest (or most appropriate for the data type). Text should be preferred – the receiving file (program, executable, web app?) is responsible for receiving data elegantly just like any other unix program would.

The concept of, say, a blog, could be transformed. I’m currently stuck with the wordpress editor if I’m using a wordpress blog. I could edit a blog post using whatever editor I wanted, as long as my blog was implemented as an HTTP API that understood how to be treated like a unix file.

This could be a library that HTTP servers could use, or it could just be a convention. It would be awesome to be able to do:

$ http://tou.herokuapp.com http://davezor.net/post/name_of_post
$ mkdir http://davezor.net/another_subdirectory
$ http://rdio.com http://davezor.net/music/pink_floyd_the_wall.mp3

Etc.