mopidy/mopidy-mpris

Standalone client

mrueg opened this issue · 3 comments

mrueg commented

As a user I'd like to run mopidy on a remote server and communicate with it using mpris.
It would be great to have a standalone version of mopidy-mpris, that runs on the client and connects to a mopidy-mpris-socket plugin via tcp / unix sockets.

This also would avoid patching mpris clients to use the system-wide dbus for communication with mopidy, if the mopidy server is run by another user.

jodal commented

I like the idea, but I'm probably not going to spend any time on this in the near future.

dz0ny commented

or just connect to existing mopidy websocket.

jodal commented

I can imagine two different solutions here:

  1. A generic MPRIS or D-Bus proxy that lets you reexport the MPRIS interface on the D-Bus bus of another system.
  2. Use the Mopidy HTTP RPC or WebSocket APIs.

A third solution as a part of Mopidy-MPRIS is out of scope for this project, so I'm closing this.