Confirmed users
920
edits
User:LesOrchard/BandwagonAPI: Difference between revisions
Jump to navigation
Jump to search
→Open Questions
LesOrchard (talk | contribs) |
|||
| Line 5: | Line 5: | ||
* How much detail about addons in collection responses is necessary for display in the extension? The less, the better, since building full addon records is expensive. | * How much detail about addons in collection responses is necessary for display in the extension? The less, the better, since building full addon records is expensive. | ||
** Add-on details only need to be included in the /api/sharing/collections/{uuid} method. I also don't think the /api/sharing/collections/{uuid}/addons/{addon guid} is necessary. [[User:Fligtar|Fligtar]] 22:10, 5 February 2009 (UTC) | ** Add-on details only need to be included in the /api/sharing/collections/{uuid} method. I also don't think the /api/sharing/collections/{uuid}/addons/{addon guid} is necessary. [[User:Fligtar|Fligtar]] 22:10, 5 February 2009 (UTC) | ||
*** Well, the question was, can we supply a minimal set of addon details in a GET /api/sharing/collections/{uuid} request for display in the addon - and if so, what's that minimal set? One of the performance issues I originally ran into with the earlier API bugs is that assembling more than 3-4 addons worth of full details can be a bear given all the joins and Cake model code. [[User:LesOrchard|LesOrchard]] 22:24, 5 February 2009 (UTC) | |||
*** Also, the /api/sharing/collections/{uuid}/addons/{addon guid} resource ''is'' necessary for the HTTP DELETE method, if we want to delete addons from collections. And if we can use a minimal set in the collection list, an HTTP GET method on this resource will return the full details for an individual addon in a collection. [[User:LesOrchard|LesOrchard]] 22:24, 5 February 2009 (UTC) | |||
* Product spec calls for ability to create collections for "auto-publishers" to sync with list of addons in browser. How is this distinguished from creating a collection in general, or is a distinction even necessary? Seems like the distinction of an auto-publisher lies mainly in the extension. | * Product spec calls for ability to create collections for "auto-publishers" to sync with list of addons in browser. How is this distinguished from creating a collection in general, or is a distinction even necessary? Seems like the distinction of an auto-publisher lies mainly in the extension. | ||
** There should probably be a field that says what type of collection something is (normal, editors pick, auto-publisher), but apart from that field, there's no difference on the API side of CRUD operations. Right now, we're only expecting auto-publishers to use the API for creation. [[User:Fligtar|Fligtar]] 22:10, 5 February 2009 (UTC) | ** There should probably be a field that says what type of collection something is (normal, editors pick, auto-publisher), but apart from that field, there's no difference on the API side of CRUD operations. Right now, we're only expecting auto-publishers to use the API for creation. [[User:Fligtar|Fligtar]] 22:10, 5 February 2009 (UTC) | ||
*** Can we get details on that field added to the product spec, along with maybe how it would affect the web frontend? [[User:LesOrchard|LesOrchard]] 22:24, 5 February 2009 (UTC) | |||
* Deleting a collection is not in the product spec, but might be useful down the road and for testing. Any harm in including it? | * Deleting a collection is not in the product spec, but might be useful down the road and for testing. Any harm in including it? | ||