I'm having a go, as a side-side project, at defining a strictly RESTful protocol for implementing DropBox-like functionality - I'm building client and server components which will be FOSS. I started this mainly as a learning experience for designing a strictly RESTful interface, but I plan to use it personally. Some random notes:
- Strictly RESTful interface (HATEOS, single base URL, server controlled namespaces)
- Simplicity over performance - easy to do everything on the command line using curl
- Supports block level transfers
So far this has stricly been for my own amusement/education - happy to write something up and put the code on github if anyone is interested.
While I was repeating myself a bit there I meant to get across that when I started I thought I knew what a RESTful interface was (nice URLs, HTTP GET/POST/PUT/DELETE) then I discovered that the term is used pretty loosely and a lot of what are described RESTful interfaces aren't really anything like what Roy Fielding meant.
- Strictly RESTful interface (HATEOS, single base URL, server controlled namespaces)
- Simplicity over performance - easy to do everything on the command line using curl
- Supports block level transfers
So far this has stricly been for my own amusement/education - happy to write something up and put the code on github if anyone is interested.