Skip to content
This repository has been archived by the owner on Apr 28, 2022. It is now read-only.

App Review & App Downloads params #3

Open
oorlov opened this issue Oct 10, 2013 · 6 comments
Open

App Review & App Downloads params #3

oorlov opened this issue Oct 10, 2013 · 6 comments

Comments

@oorlov
Copy link
Contributor

oorlov commented Oct 10, 2013

Current: App Downloads
and App Reviews

Date:

  • from [YYYY-MM-DD]
  • to [YYYY-MM-DD]

both optional?

@jesper-sjovall
Copy link
Contributor

Yes, Both date format, from and to, and I also suggests a 'limit' value for limit the result to a given number and in this case return the latest/newest of the reviews/posts.
This will get a impact of the natural sort order must be latest first and oldest last, which I think is fine for the must part of uses.

Examples: '

@jesper-sjovall
Copy link
Contributor

As suggest from #2, I also want to add country-code which I think will be must useful for only get reviews in a language that is supported by the store.
For example, on a Swedish appstore this is no to little use of reviews written in Arabic

@oorlov
Copy link
Contributor Author

oorlov commented Oct 21, 2013

Updated version of downloads :

https://www.sourceappstore.com/openaep/appreviews
?package=com.softspb.flashcards.sv - single parameter
[&datefrom=YYYY-MM-DD] - optional
[&dateto=YYYY-MM-DD] - optional
[&country=US] - optional
[&limit=100 &offsettoken= 500] - optional pair

Do paginate output there should be offset param used together with limit. And we need to return it in output like this

<?xml version="1.0" encoding="UTF-8"?>
<downloads version="1" offset=""> <!-- encoded value of request params, db state and offset -->
  <download>
...

is it simple to implement on backend?

@jesper-sjovall
Copy link
Contributor

Use

[&limit=100] - optional
[&offset=7j8ad9go] - optional

and not

[&limit=100 &offsettoken= 500] - optional pair

as in Purchases case #2 (comment)
For get a equal interface for all requests that will do the interface more easy to understand for everybody.

I think this is simple to implement on backend (for most of all systems), a loot of this will map very good to querys on for a Relational database as SQL-database.

@oorlov
Copy link
Contributor Author

oorlov commented Oct 21, 2013

OK, lets update spec

@jesper-sjovall
Copy link
Contributor

Ok, Update and I will look at it again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants