ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #08734
Re: Background services: a problem that we need to face
Am 25.06.2014 18:31, schrieb Rodney Dawes:
> On Wed, 2014-06-25 at 11:55 +0200, Rasmus Eneman wrote:
>> Other cases are Spotify and Grooveshark, neither which can use a
>> generic service. We already have one Spotify app, that only plays
>> when opened, which means that it is useless.
> This is just a bug as a result of them being webapps. Once Oxide (and
> thus the browser, and webapp-container) has support for streaming the
> audio through the persistent media player backend, then these should
> work fine as webapps.
>
> If they were native apps pushing the audio through the backend instead,
> it should already work today (ie, the same way the Music app itself
> works).
Just playing the stream over the backend won't be enough for
Grooveshark at least, looking at the API they won't the app to send
messages after 30secs and at the end of a song.
Can something like that be done as well?
>
>
>
>
>
Follow ups
References
-
Background services: a problem that we need to face
From: Fabio Colella, 2014-06-22
-
Re: Background services: a problem that we need to face
From: Thomas Voß, 2014-06-23
-
Re: Background services: a problem that we need to face
From: Fabio Colella, 2014-06-23
-
Re: Background services: a problem that we need to face
From: Thomas Voß, 2014-06-24
-
Re: Background services: a problem that we need to face
From: Benjamin Zeller, 2014-06-25
-
Re: Background services: a problem that we need to face
From: Thomas Voß, 2014-06-25
-
Re: Background services: a problem that we need to face
From: Benjamin Zeller, 2014-06-25
-
Re: Background services: a problem that we need to face
From: Michał Sawicz, 2014-06-25
-
Re: Background services: a problem that we need to face
From: Rasmus Eneman, 2014-06-25
-
Re: Background services: a problem that we need to face
From: Rodney Dawes, 2014-06-25