#musicbrainz

hi why does tagger say with most songs it cannot send to server? is it a server problem temporarily?

Vlado``: the server's fine as far as I know. What message are you getting?

in the error tab: cannot sen/receive from server

Are /any/ songs getting through for you?

half of them

half not

hmm, that's odd. The server's not showing any signs of trouble. Do you have a firewall or proxy which might be getting in the way?

Knio is now known as Knio-sleep

yalaforge_ is now known as yalaforge

yalaforge: another web service question?

ok, suppose I want to retrieve things by either name or id.

the two obvious approaches are: GET /thing/7 <- id=7

or GET /thing?id=7

is it best to pick one and be consistent, or is mixing them ok?

GET /thing/<id>

no, mixing them is no good idea

ok, so then what about using name instead of id as the key?

I'll show you a spec about our future webservice for examples

what name would that be?

select moderator by name, for example

or artist

wait a minute, ...

(mainly moderator, since name is unique)

the idea in this document is the following:

you'd have a set of moderations, available via /mod/

you can select a single one via /mod/<id>

you can search that resource (for a moderator) via /mod/?name=modname

(some kind of filtering mechanism, conceptionally)

err, /mod/?byModeratorName=modname

ok, so you're using "/<guid>" where available, and /?column=value elsewhere

and /mod/?byModeratorId=id to get all moderations by that moderator

the main problem I see with that is that it leads to ambiguities

no, it's just a coincidence that guids are available for artists, albums and tracks

mod ids are as good as guids

what kind of ambiguities?

ok. example: suppose you define two ways of fetching artists.

GET /artists/?name=.....

yup

GET /artists/?id=.....

what do you do with this query: GET /artists/?name=X&id=y ?

whatever you write in your spec :-)

you can also return an error code. that's up to you

ok :-) I like that. fine

I'll go read that document properly now. Thanks

REST is a lot more flexible than other IPC mechanisms

np. but ignore the use cases on top

we won! \o/

o_O

Knio-sleep is now known as Knio

bah. I read about cd2trm on the mailing list and it doesn't work for me :(

Knio is now known as Knio-gone

I'm getting wrong type for something

oh well.