lucifer: for the tempo/mixxx integration, we want an endpoint that allows fetching of tempo for one or more recordings, but also up to 1,000 recordings and to submit one or more tempo markups.
2025-10-30 30331, 2025
mayhem[m]
normally that would be GET/POST duo, but we need POST to do a 1,000 item GET function.
2025-10-30 30340, 2025
mayhem[m]
how can we express this in a RESTy way?
2025-10-30 30322, 2025
mayhem[m]
GET/POST and PUT? but that is inconsistent with the rest of the API.
2025-10-30 30310, 2025
lucifer[m]
mayhem: probably do two different POST endpoints
2025-10-30 30322, 2025
lucifer[m]
one for fetching and one for submissions.
2025-10-30 30327, 2025
mayhem[m]
but what to call it and still be RESTy?
2025-10-30 30354, 2025
mayhem[m]
tacking on a /submit for the submission is not document centric/
2025-10-30 30300, 2025
mayhem[m]
s///\/
2025-10-30 30308, 2025
mayhem[m]
s///
2025-10-30 30324, 2025
lucifer[m]
the POST for retrieving multiple items could /list
2025-10-30 30332, 2025
lucifer[m]
* items could be /list
2025-10-30 30354, 2025
mayhem[m]
yea, I dont see a lot of great alternatives.
2025-10-30 30354, 2025
lucifer[m]
or /search
2025-10-30 30308, 2025
mayhem[m]
/list or /batch
2025-10-30 30333, 2025
lucifer[m]
acc. to my understanding, for rest-ful GET/POST/PUT etc. concern one item. so the mutiple item listing is the separate one here.
2025-10-30 30329, 2025
mayhem[m]
agreed, we only need it because URL length limitations.
2025-10-30 30336, 2025
lucifer[m]
yup makes sense
2025-10-30 30315, 2025
lucifer[m]
single item retrieval/creation/update happen on the entity's GET/POST/PUT and the POST /entity/{list,batch,etc.} for multiple item retrieval. should be fine to call this RESTy.
2025-10-30 30313, 2025
aerozol[m] joined the channel
2025-10-30 30314, 2025
aerozol[m]
Hey mayhem, any idea of monkey's plans today? I'm meeting with him tonight/tomorrow morning but if he's going to be on soon anyway I might wait up
2025-10-30 30330, 2025
lucifer[m]
fwiw, we don't use PUT etc. in LB just POST for multiple different URLs for.
2025-10-30 30351, 2025
mayhem[m]
I have no idea, sorry. I've not gone into the office this month....
2025-10-30 30304, 2025
mayhem[m]
lucifer[m]: yes, it felt out of place.
2025-10-30 30328, 2025
aerozol[m]
All good, thanks! See ya 'tomorrow' monkey!
2025-10-30 30349, 2025
lucifer[m]
if these endpoints are going on LB/MB, i would suggest to avoid PUT just for consistency with rest of the API.
2025-10-30 30302, 2025
mayhem[m]
lucifer[m]: done.
2025-10-30 30304, 2025
monkey[m]
aerozol[m]: See you in the morning your time!
2025-10-30 30344, 2025
aerozol[m]
Oh hey! If you're up-up then it would be convenient to meet now or soon instead :)
Overall looks quite good rayyan_seliya but haven't looked into it more. Wanna open a PR so I can put it on test?
2025-10-30 30325, 2025
wargreen_ has quit
2025-10-30 30341, 2025
rayyan_seliya[m]
monkey[m]: Sure then after some little tweaks .. will open it ..
2025-10-30 30309, 2025
lazybookwyrm[m] has quit
2025-10-30 30317, 2025
rayyan_seliya[m]
Have to take care some edge cases of missing isbn olid .. etc cases ..
2025-10-30 30317, 2025
Evelynne[m]
outsidecontext: I tested picard with stemfiles... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/pUxBKohfENkcbmYfPECwvYRU>)
2025-10-30 30357, 2025
Evelynne[m]
* outsidecontext: I tested picard with stemfiles... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/VUYjDafRSWPykOaMOdBpKVCA>)
