Hi,
i'll just answer the first part in this thread for now, as i am still
looking into the other one :-)
Let me illustrate what i mean with an example:
We will use:
<artist internal-name="black_sun_empire">Black sun empire</artist>
and
<name>Digital Venom</name>
<internal-name>digital_venom</internal-name>
So for the artist, the search:
http://api.digital-tunes.net/releases/by_artist/black_sun_empire?key=666
will fail. and only:
http://api.digital-tunes.net/releases/by_artist/black%20sun%20empire?key=666
will be successful.
So a search by internal name will fail.
For labels we have a different story, in this case the following two
api requests will be successful:
http://api.digital-tunes.net/releases/by_label/digital%20venom?key=666
http://api.digital-tunes.net/releases/by_label/digital_venom?key=666
ergo: both the name and the internal-name can be used.
I hope this makes it clear
As far as features i'll ponder on it for a while, but until now i'm a
happy chappy!
cheers
esc
On Mar 27, 11:51 am, will-c <
william.coa...@gmail.com> wrote:
> Hey cool stuff :D
>
> > 1) I can search labels by the internal name, but not the artists.
>
> Not sure what you mean here, as far as i know there is no way to
> search for labels by internal name, calls to /labels/ query using
> name.
>
> 2) The way i parse the xml now is a bit hacky, maybe if i had a DTD it
> would be easier to marshall/unmarshall the xml.
>
> Not sure if a DTD would make your life much easier... Im sure there
> must be all kinds of nice Python xml parsing libs out there, but im
> not a Python guy so wouldnt know. I have played around in the past
> with roxmlhttp://
roxml.rubyforge.org/for ruby, i guess you could use