CACHING DETAILS
Reported by sudara | 2009-12-21 17:05:20 UTC
Things to test:
Asset caching:
- Playback works.
- Commenting works.
- date changes even though item is cached (by default uploaded at
will only change when asset is listened to
- Asset detail changes => cache invalidated
- Favs / Playcount changes => cache invalidated
- Does hourly cronjob "update_hotness" invalidate cache? It shouldn't, this would be bad.
Comments and changes to this ticket
-
sudara 2009-12-21 17:20:01 UTC
- Tag set to “ar, backend”
-
sudara 2009-12-21 17:23:20 UTC
Just fixed the update_hotness
Confirmed that playing invalidates cache (changes listen count)
Commenting invalidates cache.
Still left to do:
1) dates move into javascript
2) Favorites invalidate cache -
-
sudara 2010-01-10 05:22:02 UTC
Working on:
- Admin info
- dates move into js
- favs invalidate cache (is this needed since plays invalidate cache?)
- Remove "first playlist" - dropping features ftw.
-
sudara 2010-01-10 05:26:56 UTC
Done:
* removed "first playlist" - so long, useless sketchy feature! * Render admin stuff by defaultTo do:
* dates into js (uploaded at....) * favs invalidate cache (needed? this might not be, since plays invalidate cache) * upload to staging * give link to admin/moderator to show admin stuff -
sudara 2010-01-11 13:38:04 UTC
Checklist:
1) Playback works :)
2) Edit buttons only show for admin and owners
3) Commenting works
3) Date of upload changes and is correct -
sudara 2010-01-20 07:37:43 UTC
- State changed from “new” to “resolved”
- Assigned user set to “sudara”
DONE BABY. NOW TEH BUGZ A COMING.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
kick ass musician's home.
sudara