Hi, > - does UDD provide a mechanism for detecting when data is stale, so that > GET requests don't always have to run an SQL query?
Running SQL queries multiple time is not a problem per se because they are cached at the database level. There is currently no way to check if data has changed in DMD; another bug would benefit adding this feature: rss feeds get updated on every pull due to pubdate set to "now" (#749534). At least one other bug should be considered if database is modified: it would be useful to have a comment field/column for TODOs in DMD (#750999). One way to implement this: add a dashboard_todo table with the data currently computed by web/inc/dmd-data.rb, with an additional field for storing the row creation time and eventually with a comments field. The table is updated hourly for instance, so when a group of email adresses and/or packages ask for their todos the application would then be able to find the last todo creation date and infer if data is stale. > - how could multiple feeds be supported? E.g. some developers may want > a single task item in their to-do list that says "Fix RC bugs" while > other developers may want to see each RC bug as a separate to-do item. > Is there any plan to give such options for the RSS feed too? I do not know. > - it would be good to include in the feeds (both RSS and CalDAV) bugs > that the developer has submitted to some other package and they have the > moreinfo tag Agreed. > - it may also be useful to filter out bugs that the developer has put > the moreinfo tag on within the last 2 weeks (or maybe 1-2 days if the > bug is RC) so the developer can focus on those bugs that he hasn't > looked at already Cheers, Christophe -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150114120509.GA4209@atitude.localdomain
