api/documentation inconsistencies
15 views
Skip to first unread message
Stefan Kersten
Oct 30, 2012, 1:08:14 PM10/30/12
to freeso...@googlegroups.com
hi again,
i've found some more api/documentation quirks:
* in Sound Geotags resource parameters: min_lom should be min_lon (or min_lomo?)
* user packs response: "reduced version of the Pack response" contains "description" which is not contained in the Pack response
* the user sounds response doesn't contain the user record (for saving bandwidth?); this is a problem in a statically typed language, because the response type changes from "reduced version of Sound response" to "even more reduced version of Sound response" and basically requires a different response type for each type of request ... maybe the sounds response could be unified to include the user (even if it's redundant)?
thanks,
<sk>
i've found some more api/documentation quirks:
* in Sound Geotags resource parameters: min_lom should be min_lon (or min_lomo?)
* user packs response: "reduced version of the Pack response" contains "description" which is not contained in the Pack response
* the user sounds response doesn't contain the user record (for saving bandwidth?); this is a problem in a statically typed language, because the response type changes from "reduced version of Sound response" to "even more reduced version of Sound response" and basically requires a different response type for each type of request ... maybe the sounds response could be unified to include the user (even if it's redundant)?
thanks,
<sk>
Stefan Kersten
Oct 30, 2012, 1:32:02 PM10/30/12
to freeso...@googlegroups.com
sorry for replying to my own post ...
On 30.10.2012, at 18:08, Stefan Kersten wrote:
> * the user sounds response doesn't contain the user record (for saving bandwidth?); this is a problem in a statically typed language, because the response type changes from "reduced version of Sound response" to "even more reduced version of Sound response" and basically requires a different response type for each type of request ... maybe the sounds response could be unified to include the user (even if it's redundant)?
just noticed that the user field is also missing from the pack sounds response.
<sk>
On 30.10.2012, at 18:08, Stefan Kersten wrote:
> * the user sounds response doesn't contain the user record (for saving bandwidth?); this is a problem in a statically typed language, because the response type changes from "reduced version of Sound response" to "even more reduced version of Sound response" and basically requires a different response type for each type of request ... maybe the sounds response could be unified to include the user (even if it's redundant)?
<sk>
frederic font corbera
Nov 5, 2012, 8:57:45 AM11/5/12
to freeso...@googlegroups.com
Hello sk,
* in Sound Geotags resource parameters: min_lom should be min_lon (or min_lomo?)
should be min_lon, that is a bug in the documentation...
* user packs response: "reduced version of the Pack response" contains "description" which is not contained in the Pack response
another bug, actually description is not included in any pack response. it will be included in the pack resource but not in the lists of packs (alhtough only a few packs have descriptions!)
* the user sounds response doesn't contain the user record (for saving bandwidth?); this is a problem in a statically typed language, because the response type changes from "reduced version of Sound response" to "even more reduced version of Sound response" and basically requires a different response type for each type of request ... maybe the sounds response could be unified to include the user (even if it's redundant)?
user sounds response does not has the user field because you already must know who is the user to call its "sounds" method. however, I agree that for the sake of unification it should be added. it will also be added to the pack sounds resource.
frederic
--
frederic font corbera
Nov 5, 2012, 9:10:33 AM11/5/12
to freeso...@googlegroups.com
docs and api updated!
frederic
Stefan Kersten
Nov 5, 2012, 9:52:39 AM11/5/12
to freeso...@googlegroups.com
hey frederic,
On 05.11.2012, at 15:10, frederic font corbera wrote:
> docs and api updated!
great, thanks!
<sk>
On 05.11.2012, at 15:10, frederic font corbera wrote:
> docs and api updated!
great, thanks!
<sk>
Reply all
Reply to author
Forward
0 new messages