This repository has been archived by the owner on Feb 24, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
Home
Marcin Kurczewski edited this page Jul 29, 2013
·
19 revisions
- What to do with users that are queued, and then it turns out they do not exist on MAL?
Do quick ajax request?
- Dequeuing users: When you visit any user page regardless whether it's cached or not, ready to be served or not - add the user to queue. Back end should pick up users from queue and immediately remove them before processing.
- Back end control flow:
- Pick up queued users,
- Download their stuff and put it into DB (
UserProcessor
), - Download missing or old anime/manga stuff and put it into DB (
AnimeProcessor
,MangaProcessor
), Render content for all users that were just downloaded (*Controller
),Render global data (GlobalDataPresenter
).
- Front end control flow:
- Queue users into back end,
- If cache exists:
- Send the cache
- Otherwise:
- If user exists in local DB:
- render and save cache, then send the cache,
- Otherwise:
- Display friendly message that user does not exists and he was put in the processing queue.
- If user exists in local DB:
- Back end operating mode - for now, let's assume it should pick up maximally
n
users every run and use control flow described above. - User settings regarding image colors - when tweaking settings, bypass proxy, else read cached image
- Cache generation - pages shouldn't be generated in cron