title: Feathers custom service methods -- against the rules
body: <p>The Feathers framework is designed to stick to the REST design, I know, but I think I have an edge case that is worthy of breaking the rules a bit. I want to make a music player API that allows programmatic access to the player controls via HTTP and Socket.io.</p>
  
  <p>The player, however, isn't a simple case of <code>get</code>, <code>put</code>, <code>patch</code>, <code>post</code>, and <code>delete</code>. One player will be created for every user and will never be deleted, only altered. I want custom methods like play, pause, setQueue, etc. on subroutes of the method, for example <code>PATCH /player/play</code> and <code>PATCH /player/pause</code>.</p>
  
  <p>This is exactly <a href="https://developer.spotify.com/web-api/start-a-users-playback/" rel="nofollow noreferrer">how Spotify does it in their API</a>, and it makes much more sense than sending a <code>PATCH</code> request to the same endpoint each time and updating the player data manually, ie. <code>PATCH /player {nowPlaying: {index: newIndex}}</code> to skip to the next track, where the user of the API has to know the schema of the player data and how it operates. Instead, something like <code>PATCH /player/next</code> makes much more sense and is easier to use.</p>
  
  <p>How do I implement a service like this using Feathers' API without doing it all manually in express? If it's not possible, what's the most friendly way to integrate the custom express code nicely with the rest of the app?</p>