Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Custom Tag(s) Search For API Source #17

Open
ghost opened this issue Oct 13, 2013 · 0 comments
Open

Support Custom Tag(s) Search For API Source #17

ghost opened this issue Oct 13, 2013 · 0 comments

Comments

@ghost
Copy link

ghost commented Oct 13, 2013

Right now the posts that are queried for the API backlog source are narrowed down to just the [php] tag. I would like to add the ability to have a user choose which tag(s) they want to search under for bad posts. This feature is dependent on Issue #15 being fixed, otherwise it's a guarantee the server will be banned constantly. Each tag of course will be cached separately from each other in their own cache file.

Here is how I see the process happening, feel free to make changes:

  1. User chooses new tag(s)
  2. The backlog queues the new tag(s) to be queried and cached
  3. Once the tags have been queried and we now have results, display the results
    If multiple tags are chosen we display them as one result, but in chronological order.

Things to consider:

  1. How will cache updating happen?
    • Do we update ALL tags that have been used in backlog?
    • The most popular tags based on popularity on SO?
    • The most popular tags based on people trying to use that tag in the backlog?
  2. Backlog will need an updater service to handle the cache updating and queue
  3. Cron will be run every two minutes as usual, but will be dependent on the updater service handling the cache updating as well as processing tag queue
  4. Can we offload the API queries to client-side since it is just a JSON response that way it won't count against the server's request and prevent banning?

This is in no way happening anytime soon, but would like some insight on how it might be done best so can plan ahead. So, thoughts?


Related reading: https://github.com/Crell/fig-standards/blob/Cache/proposed/cache.md

@ghost ghost self-assigned this Jan 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants