On Thu, Oct 15, 2015 at 2:13 PM, Tom Quarendon <[email protected]> wrote: >> The ZeroMQ XRAP spec has nothing to do with RestTL, just to be clear. > Well, other than the fact that the words are lifted almost verbatim?
Let me rephrase that... XRAP is a reboot of RestTL, over ZeroMQ, however as RestTL predates ZeroMQ, it's unlikely anyone on this list except myself knows the relevance of that. > But what if I wanted albums to be public resources too? What would GET /music > then return? Playlists or albums? Surely it would be more natural to have GET > /music/playlist and GET /music/album as appears normal "resource oriented" > practice? By design you cannot have multiple public resources. That would mean you need to agree upfront on naming conventions for these. Upfront consensus etc. The XRAP model is to navigate a single root resource. You can have multiple root resources, for sure. You hit a naming problem as you need a name for the container. You can of course put albums and playlists into /music and GET them all in one go, then create inside /music. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
