On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
> It could be useful yes. Let me add to my list...
My playlist is set once for all before playback, so I'll need to
schedule N "next" requests.
Without this, I'll have to add an arbitrary number of "next" tracks.
More globally, the major problem with the api is that it is requires
the client to be stateful.
One example: you have to keep track of the mix_id to be able to report
playback. (Not provided in play request).
On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
<fcarteg...@gmail.com> wrote:
> On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
>> It could be useful yes. Let me add to my list...
> My playlist is set once for all before playback, so I'll need to
> schedule N "next" requests.
> Without this, I'll have to add an arbitrary number of "next" tracks.
> More globally, the major problem with the api is that it is requires
> the client to be stateful.
> One example: you have to keep track of the mix_id to be able to report
> playback. (Not provided in play request).
Does the same parameter apply when mixes.json is called? If not, could you
please add it? It would be useful for the users to know how big are the
mixes when choosing which one to play.
cheers,
Matija
On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <r...@8tracks.com> wrote:
> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
> <fcarteg...@gmail.com> wrote:
> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
> >> It could be useful yes. Let me add to my list...
> > My playlist is set once for all before playback, so I'll need to
> > schedule N "next" requests.
> > Without this, I'll have to add an arbitrary number of "next" tracks.
> > More globally, the major problem with the api is that it is requires
> > the client to be stateful.
> > One example: you have to keep track of the mix_id to be able to report
> > playback. (Not provided in play request).
On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <matij...@gmail.com> wrote:
> Cool, a very nice new feature!
> Does the same parameter apply when mixes.json is called? If not, could you
> please add it? It would be useful for the users to know how big are the
> mixes when choosing which one to play.
> cheers,
> Matija
> On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <r...@8tracks.com> wrote:
>> Hey Francois, it took a long time but we did add tracks_count &
>> duration to the API.
>> You can get them by including "length" in your requests, for instance:
>> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
>> <fcarteg...@gmail.com> wrote:
>> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
>> >> It could be useful yes. Let me add to my list...
>> > My playlist is set once for all before playback, so I'll need to
>> > schedule N "next" requests.
>> > Without this, I'll have to add an arbitrary number of "next" tracks.
>> > More globally, the major problem with the api is that it is requires
>> > the client to be stateful.
>> > One example: you have to keep track of the mix_id to be able to report
>> > playback. (Not provided in play request).
> Thanks Matija, which call are you thinking about exactly?
> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <matij...@gmail.com> wrote:
> > Cool, a very nice new feature!
> > Does the same parameter apply when mixes.json is called? If not, could
> you
> > please add it? It would be useful for the users to know how big are the
> > mixes when choosing which one to play.
> > cheers,
> > Matija
> > On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <r...@8tracks.com>
> wrote:
> >> Hey Francois, it took a long time but we did add tracks_count &
> >> duration to the API.
> >> You can get them by including "length" in your requests, for instance:
> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
> >> <fcarteg...@gmail.com> wrote:
> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
> >> >> It could be useful yes. Let me add to my list...
> >> > My playlist is set once for all before playback, so I'll need to
> >> > schedule N "next" requests.
> >> > Without this, I'll have to add an arbitrary number of "next" tracks.
> >> > More globally, the major problem with the api is that it is requires
> >> > the client to be stateful.
> >> > One example: you have to keep track of the mix_id to be able to report
> >> > playback. (Not provided in play request).
> On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <r...@8tracks.com> wrote:
>> Thanks Matija, which call are you thinking about exactly?
>> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <matij...@gmail.com> wrote:
>> > Cool, a very nice new feature!
>> > Does the same parameter apply when mixes.json is called? If not, could
>> > you
>> > please add it? It would be useful for the users to know how big are the
>> > mixes when choosing which one to play.
>> > cheers,
>> > Matija
>> > On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <r...@8tracks.com>
>> > wrote:
>> >> Hey Francois, it took a long time but we did add tracks_count &
>> >> duration to the API.
>> >> You can get them by including "length" in your requests, for instance:
>> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
>> >> <fcarteg...@gmail.com> wrote:
>> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
>> >> >> It could be useful yes. Let me add to my list...
>> >> > My playlist is set once for all before playback, so I'll need to
>> >> > schedule N "next" requests.
>> >> > Without this, I'll have to add an arbitrary number of "next" tracks.
>> >> > More globally, the major problem with the api is that it is requires
>> >> > the client to be stateful.
>> >> > One example: you have to keep track of the mix_id to be able to
>> >> > report
>> >> > playback. (Not provided in play request).
I didn't find an answer in the API documentation, so I ask in this thread:
Is there yet a possible way to fetch the length of a mix when using the mixes.xml? Or do I have to query every mix on his own (/mixes/[id].xml)?
I would like to include the playing duration to my mix overview as easy as possible, so it would be great if tracks_count & duration would be part of the mixes.xml response too :)
Greets, Markus
Am Samstag, 22. September 2012 01:53:44 UTC+2 schrieb Remi Gabillet:
> > On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <re...@8tracks.com<javascript:>> > wrote:
> >> Thanks Matija, which call are you thinking about exactly?
> >> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <mati...@gmail.com<javascript:>> > wrote: > >> > Cool, a very nice new feature!
> >> > Does the same parameter apply when mixes.json is called? If not, > could > >> > you > >> > please add it? It would be useful for the users to know how big are > the > >> > mixes when choosing which one to play.
> >> > cheers, > >> > Matija
> >> > On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <re...@8tracks.com<javascript:>>
> >> > wrote:
> >> >> Hey Francois, it took a long time but we did add tracks_count & > >> >> duration to the API.
> >> >> You can get them by including "length" in your requests, for > instance:
> >> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie > >> >> <fcart...@gmail.com <javascript:>> wrote: > >> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote: > >> >> >> It could be useful yes. Let me add to my list...
> >> >> > My playlist is set once for all before playback, so I'll need to > >> >> > schedule N "next" requests. > >> >> > Without this, I'll have to add an arbitrary number of "next" > tracks.
> >> >> > More globally, the major problem with the api is that it is > requires > >> >> > the client to be stateful. > >> >> > One example: you have to keep track of the mix_id to be able to > >> >> > report > >> >> > playback. (Not provided in play request).
We have a newer API that lets you adjust which fields you want to be
returned but it's not fully baked yet.
For now, I just added these 2 fields (tracks_count and duration) to
all version 2 requests (to be deployed later today).
On Thu, Jan 31, 2013 at 6:56 AM, Mika <markus...@yahoo.de> wrote:
> Hey Remi.
> I didn't find an answer in the API documentation, so I ask in this thread:
> Is there yet a possible way to fetch the length of a mix when using the
> mixes.xml? Or do I have to query every mix on his own (/mixes/[id].xml)?
> I would like to include the playing duration to my mix overview as easy as
> possible, so it would be great if tracks_count & duration would be part of
> the mixes.xml response too :)
> Greets, Markus
> Am Samstag, 22. September 2012 01:53:44 UTC+2 schrieb Remi Gabillet:
>> Unfortunately that's not possible yet but I'm hoping to improve our
>> API backend to allow this kind of query easily.
>> On Wed, Sep 19, 2012 at 12:31 AM, Matija Lukic <mati...@gmail.com> wrote:
>> > Hi,
>> > On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <re...@8tracks.com>
>> > wrote:
>> >> Thanks Matija, which call are you thinking about exactly?
>> >> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <mati...@gmail.com>
>> >> wrote:
>> >> > Cool, a very nice new feature!
>> >> > Does the same parameter apply when mixes.json is called? If not,
>> >> > could
>> >> > you
>> >> > please add it? It would be useful for the users to know how big are
>> >> > the
>> >> > mixes when choosing which one to play.
>> >> > cheers,
>> >> > Matija
>> >> > On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <re...@8tracks.com>
>> >> > wrote:
>> >> >> Hey Francois, it took a long time but we did add tracks_count &
>> >> >> duration to the API.
>> >> >> You can get them by including "length" in your requests, for
>> >> >> instance:
>> >> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
>> >> >> <fcart...@gmail.com> wrote:
>> >> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
>> >> >> >> It could be useful yes. Let me add to my list...
>> >> >> > My playlist is set once for all before playback, so I'll need to
>> >> >> > schedule N "next" requests.
>> >> >> > Without this, I'll have to add an arbitrary number of "next"
>> >> >> > tracks.
>> >> >> > More globally, the major problem with the api is that it is
>> >> >> > requires
>> >> >> > the client to be stateful.
>> >> >> > One example: you have to keep track of the mix_id to be able to
>> >> >> > report
>> >> >> > playback. (Not provided in play request).
> --
> You received this message because you are subscribed to the Google Groups
> "8tracks public API" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 8tracks-public-api+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> We have a newer API that lets you adjust which fields you want to be > returned but it's not fully baked yet. > For now, I just added these 2 fields (tracks_count and duration) to > all version 2 requests (to be deployed later today).
> Happy to help!
> Remi
> On Thu, Jan 31, 2013 at 6:56 AM, Mika <mark...@yahoo.de <javascript:>> > wrote: > > Hey Remi.
> > I didn't find an answer in the API documentation, so I ask in this > thread: > > Is there yet a possible way to fetch the length of a mix when using the > > mixes.xml? Or do I have to query every mix on his own (/mixes/[id].xml)?
> > I would like to include the playing duration to my mix overview as easy > as > > possible, so it would be great if tracks_count & duration would be part > of > > the mixes.xml response too :)
> > Greets, Markus
> > Am Samstag, 22. September 2012 01:53:44 UTC+2 schrieb Remi Gabillet:
> >> Unfortunately that's not possible yet but I'm hoping to improve our > >> API backend to allow this kind of query easily.
> >> On Wed, Sep 19, 2012 at 12:31 AM, Matija Lukic <mati...@gmail.com> > wrote: > >> > Hi,
> >> > On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <re...@8tracks.com> > >> > wrote:
> >> >> Thanks Matija, which call are you thinking about exactly?
> >> >> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <mati...@gmail.com> > >> >> wrote: > >> >> > Cool, a very nice new feature!
> >> >> > Does the same parameter apply when mixes.json is called? If not, > >> >> > could > >> >> > you > >> >> > please add it? It would be useful for the users to know how big > are > >> >> > the > >> >> > mixes when choosing which one to play.
> >> >> > cheers, > >> >> > Matija
> >> >> > On Tue, Sep 18, 2012 at 3:53 AM, Remi - 8tracks <re...@8tracks.com>
> >> >> > wrote:
> >> >> >> Hey Francois, it took a long time but we did add tracks_count & > >> >> >> duration to the API.
> >> >> >> You can get them by including "length" in your requests, for > >> >> >> instance:
> >> >> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie > >> >> >> <fcart...@gmail.com> wrote: > >> >> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote: > >> >> >> >> It could be useful yes. Let me add to my list...
> >> >> >> > My playlist is set once for all before playback, so I'll need > to > >> >> >> > schedule N "next" requests. > >> >> >> > Without this, I'll have to add an arbitrary number of "next" > >> >> >> > tracks.
> >> >> >> > More globally, the major problem with the api is that it is > >> >> >> > requires > >> >> >> > the client to be stateful. > >> >> >> > One example: you have to keep track of the mix_id to be able to > >> >> >> > report > >> >> >> > playback. (Not provided in play request).
> > -- > > You received this message because you are subscribed to the Google > Groups > > "8tracks public API" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to 8tracks-public-api+unsubscribe@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out.
> Am Donnerstag, 31. Januar 2013 16:56:08 UTC+1 schrieb Remi Gabillet:
>> Hi Markus,
>> We have a newer API that lets you adjust which fields you want to be
>> returned but it's not fully baked yet.
>> For now, I just added these 2 fields (tracks_count and duration) to
>> all version 2 requests (to be deployed later today).
>> Happy to help!
>> Remi
>> On Thu, Jan 31, 2013 at 6:56 AM, Mika <mark...@yahoo.de> wrote:
>> > Hey Remi.
>> > I didn't find an answer in the API documentation, so I ask in this
>> > thread:
>> > Is there yet a possible way to fetch the length of a mix when using the
>> > mixes.xml? Or do I have to query every mix on his own (/mixes/[id].xml)?
>> > I would like to include the playing duration to my mix overview as easy
>> > as
>> > possible, so it would be great if tracks_count & duration would be part
>> > of
>> > the mixes.xml response too :)
>> > Greets, Markus
>> > Am Samstag, 22. September 2012 01:53:44 UTC+2 schrieb Remi Gabillet:
>> >> Unfortunately that's not possible yet but I'm hoping to improve our
>> >> API backend to allow this kind of query easily.
>> >> On Wed, Sep 19, 2012 at 12:31 AM, Matija Lukic <mati...@gmail.com>
>> >> wrote:
>> >> > Hi,
>> >> > On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <re...@8tracks.com>
>> >> > wrote:
>> >> >> Thanks Matija, which call are you thinking about exactly?
>> >> >> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <mati...@gmail.com>
>> >> >> wrote:
>> >> >> > Cool, a very nice new feature!
>> >> >> > Does the same parameter apply when mixes.json is called? If not,
>> >> >> > could
>> >> >> > you
>> >> >> > please add it? It would be useful for the users to know how big
>> >> >> > are
>> >> >> > the
>> >> >> > mixes when choosing which one to play.
>> >> >> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie
>> >> >> >> <fcart...@gmail.com> wrote:
>> >> >> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote:
>> >> >> >> >> It could be useful yes. Let me add to my list...
>> >> >> >> > My playlist is set once for all before playback, so I'll need
>> >> >> >> > to
>> >> >> >> > schedule N "next" requests.
>> >> >> >> > Without this, I'll have to add an arbitrary number of "next"
>> >> >> >> > tracks.
>> >> >> >> > More globally, the major problem with the api is that it is
>> >> >> >> > requires
>> >> >> >> > the client to be stateful.
>> >> >> >> > One example: you have to keep track of the mix_id to be able to
>> >> >> >> > report
>> >> >> >> > playback. (Not provided in play request).
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "8tracks public API" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to 8tracks-public-api+unsubscribe@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
> --
> You received this message because you are subscribed to the Google Groups
> "8tracks public API" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 8tracks-public-api+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> > and fetch the duration property of the mixes. > > Great :)
> > Greets, Markus
> > Am Donnerstag, 31. Januar 2013 16:56:08 UTC+1 schrieb Remi Gabillet:
> >> Hi Markus,
> >> We have a newer API that lets you adjust which fields you want to be > >> returned but it's not fully baked yet. > >> For now, I just added these 2 fields (tracks_count and duration) to > >> all version 2 requests (to be deployed later today).
> >> Happy to help!
> >> Remi
> >> On Thu, Jan 31, 2013 at 6:56 AM, Mika <mark...@yahoo.de> wrote: > >> > Hey Remi.
> >> > I didn't find an answer in the API documentation, so I ask in this > >> > thread: > >> > Is there yet a possible way to fetch the length of a mix when using > the > >> > mixes.xml? Or do I have to query every mix on his own > (/mixes/[id].xml)?
> >> > I would like to include the playing duration to my mix overview as > easy > >> > as > >> > possible, so it would be great if tracks_count & duration would be > part > >> > of > >> > the mixes.xml response too :)
> >> > Greets, Markus
> >> > Am Samstag, 22. September 2012 01:53:44 UTC+2 schrieb Remi Gabillet:
> >> >> Unfortunately that's not possible yet but I'm hoping to improve our > >> >> API backend to allow this kind of query easily.
> >> >> On Wed, Sep 19, 2012 at 12:31 AM, Matija Lukic <mati...@gmail.com> > >> >> wrote: > >> >> > Hi,
> >> >> > On Wed, Sep 19, 2012 at 4:54 AM, Remi - 8tracks <re...@8tracks.com>
> >> >> > wrote:
> >> >> >> Thanks Matija, which call are you thinking about exactly?
> >> >> >> On Tue, Sep 18, 2012 at 4:56 PM, Matija Lukic <mati...@gmail.com>
> >> >> >> wrote: > >> >> >> > Cool, a very nice new feature!
> >> >> >> > Does the same parameter apply when mixes.json is called? If > not, > >> >> >> > could > >> >> >> > you > >> >> >> > please add it? It would be useful for the users to know how big > >> >> >> > are > >> >> >> > the > >> >> >> > mixes when choosing which one to play.
> >> >> >> >> On Wed, Jun 20, 2012 at 11:38 AM, Francois Cartegnie > >> >> >> >> <fcart...@gmail.com> wrote: > >> >> >> >> > On 20 juin, 18:32, Remi - 8tracks <r...@8tracks.com> wrote: > >> >> >> >> >> It could be useful yes. Let me add to my list...
> >> >> >> >> > My playlist is set once for all before playback, so I'll > need > >> >> >> >> > to > >> >> >> >> > schedule N "next" requests. > >> >> >> >> > Without this, I'll have to add an arbitrary number of "next" > >> >> >> >> > tracks.
> >> >> >> >> > More globally, the major problem with the api is that it is > >> >> >> >> > requires > >> >> >> >> > the client to be stateful. > >> >> >> >> > One example: you have to keep track of the mix_id to be able > to > >> >> >> >> > report > >> >> >> >> > playback. (Not provided in play request).
> >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "8tracks public API" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send > >> > an > >> > email to 8tracks-public-api+unsubscribe@googlegroups.com<javascript:>.
> > -- > > You received this message because you are subscribed to the Google > Groups > > "8tracks public API" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to 8tracks-public-api+unsubscribe@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out.
