-
Vlado`` joined the channel
2004-12-19 35412, 2004
-
Vlado``
hi why does tagger say with most songs it cannot send to server? is it a server problem temporarily?
2004-12-19 35459, 2004
-
djce
Vlado``: the server's fine as far as I know. What message are you getting?
2004-12-19 35454, 2004
-
Vlado``
in the error tab: cannot sen/receive from server
2004-12-19 35417, 2004
-
djce
Are /any/ songs getting through for you?
2004-12-19 35426, 2004
-
Vlado``
half of them
2004-12-19 35428, 2004
-
Vlado``
half not
2004-12-19 35404, 2004
-
djce
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?
2004-12-19 35451, 2004
-
djce has quit
2004-12-19 35449, 2004
-
Vlado`` has quit
2004-12-19 35441, 2004
-
]Thread[ joined the channel
2004-12-19 35446, 2004
-
]Thread[ has quit
2004-12-19 35415, 2004
-
spooge joined the channel
2004-12-19 35401, 2004
-
yalaforge joined the channel
2004-12-19 35458, 2004
-
Knio
Knio is now known as Knio-sleep
2004-12-19 35449, 2004
-
djce joined the channel
2004-12-19 35424, 2004
-
yalaforge_ joined the channel
2004-12-19 35458, 2004
-
yalaforge has quit
2004-12-19 35415, 2004
-
yalaforge_
yalaforge_ is now known as yalaforge
2004-12-19 35450, 2004
-
yalaforge is away: lunch
2004-12-19 35450, 2004
-
yalaforge is back (gone 01:11:00)
2004-12-19 35415, 2004
-
spooge has quit
2004-12-19 35418, 2004
-
spooge joined the channel
2004-12-19 35419, 2004
-
djce
yalaforge: another web service question?
2004-12-19 35432, 2004
-
yalaforge
yup?
2004-12-19 35448, 2004
-
djce
ok, suppose I want to retrieve things by either name or id.
2004-12-19 35412, 2004
-
djce
the two obvious approaches are: GET /thing/7 <- id=7
2004-12-19 35419, 2004
-
djce
or GET /thing?id=7
2004-12-19 35432, 2004
-
djce
is it best to pick one and be consistent, or is mixing them ok?
2004-12-19 35436, 2004
-
yalaforge
GET /thing/<id>
2004-12-19 35444, 2004
-
yalaforge
no, mixing them is no good idea
2004-12-19 35458, 2004
-
djce
ok, so then what about using name instead of id as the key?
2004-12-19 35401, 2004
-
yalaforge
I'll show you a spec about our future webservice for examples
2004-12-19 35415, 2004
-
yalaforge
what name would that be?
2004-12-19 35427, 2004
-
djce
select moderator by name, for example
2004-12-19 35428, 2004
-
djce
or artist
2004-12-19 35439, 2004
-
yalaforge
wait a minute, ...
2004-12-19 35440, 2004
-
djce
(mainly moderator, since name is unique)
2004-12-19 35405, 2004
-
yalaforge
2004-12-19 35424, 2004
-
yalaforge
the idea in this document is the following:
2004-12-19 35445, 2004
-
yalaforge
you'd have a set of moderations, available via /mod/
2004-12-19 35456, 2004
-
yalaforge
you can select a single one via /mod/<id>
2004-12-19 35417, 2004
-
yalaforge
you can search that resource (for a moderator) via /mod/?name=modname
2004-12-19 35442, 2004
-
yalaforge
(some kind of filtering mechanism, conceptionally)
2004-12-19 35408, 2004
-
yalaforge
err, /mod/?byModeratorName=modname
2004-12-19 35426, 2004
-
djce
ok, so you're using "/<guid>" where available, and /?column=value elsewhere
2004-12-19 35431, 2004
-
yalaforge
and /mod/?byModeratorId=id to get all moderations by that moderator
2004-12-19 35406, 2004
-
djce
the main problem I see with that is that it leads to ambiguities
2004-12-19 35411, 2004
-
yalaforge
no, it's just a coincidence that guids are available for artists, albums and tracks
2004-12-19 35419, 2004
-
yalaforge
mod ids are as good as guids
2004-12-19 35428, 2004
-
yalaforge
what kind of ambiguities?
2004-12-19 35444, 2004
-
djce
ok. example: suppose you define two ways of fetching artists.
2004-12-19 35452, 2004
-
djce
GET /artists/?name=.....
2004-12-19 35459, 2004
-
yalaforge
yup
2004-12-19 35401, 2004
-
djce
GET /artists/?id=.....
2004-12-19 35417, 2004
-
djce
what do you do with this query: GET /artists/?name=X&id=y ?
2004-12-19 35432, 2004
-
yalaforge
whatever you write in your spec :-)
2004-12-19 35453, 2004
-
yalaforge
you can also return an error code. that's up to you
2004-12-19 35407, 2004
-
djce
ok :-) I like that. fine
2004-12-19 35438, 2004
-
djce
I'll go read that document properly now. Thanks
2004-12-19 35442, 2004
-
yalaforge
REST is a lot more flexible than other IPC mechanisms
2004-12-19 35452, 2004
-
yalaforge
np. but ignore the use cases on top
2004-12-19 35439, 2004
-
yalaforge is away: to boldly go ...
2004-12-19 35450, 2004
-
wheels has quit
2004-12-19 35432, 2004
-
yalaforge is back (gone 01:11:53)
2004-12-19 35434, 2004
-
yalaforge has quit
2004-12-19 35417, 2004
-
djce has quit
2004-12-19 35407, 2004
-
canidae chants "noooorwaay, norway, norway, nooooooooorwaaaaaaaay!" :D
2004-12-19 35415, 2004
-
canidae
we won! \o/
2004-12-19 35459, 2004
-
cikkolata
o_O
2004-12-19 35456, 2004
-
Knio-sleep
Knio-sleep is now known as Knio
2004-12-19 35457, 2004
-
real joined the channel
2004-12-19 35416, 2004
-
Kanmu joined the channel
2004-12-19 35420, 2004
-
Kanmu has quit
2004-12-19 35421, 2004
-
Kanmu joined the channel
2004-12-19 35441, 2004
-
wheels joined the channel
2004-12-19 35418, 2004
-
real has quit
2004-12-19 35415, 2004
-
yalaforge joined the channel
2004-12-19 35455, 2004
-
cikkolata
bah. I read about cd2trm on the mailing list and it doesn't work for me :(
2004-12-19 35449, 2004
-
Knio
Knio is now known as Knio-gone
2004-12-19 35415, 2004
-
yalaforge wrote a script in perl but the perl bindings lack proper trm submission functions
2004-12-19 35401, 2004
-
cikkolata
I'm getting wrong type for something
2004-12-19 35446, 2004
-
cikkolata
oh well.
2004-12-19 35455, 2004
-
cikkolata rips the CD as she's been meaning to.
2004-12-19 35420, 2004
-
yalaforge has quit
2004-12-19 35412, 2004
-
m_wheels joined the channel
2004-12-19 35436, 2004
-
wheels has quit
