touch-packages team mailing list archive

[Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>]

Added info: Today scope uses ResultsTtlType=Large currently.

Balancing the rate of auto refresh of the today scope has proven
interesting since we want it refreshed often enough that the Day info
(and other info) is correct and sufficiently reliable, but also
refreshed infrequently enough that users are not disrupted by too much
auto-refreshing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1500467

Title:
  Aggregator reloading needs rethinking

Status in Today Scope:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Today scope is basically a place-holder for 'sub scopes'. The
  today scope has three problems which cannot both be resolved under the
  current system. These are:

  1) The scope is reloading at times I do not want it to
  2) The scope has not got the latest data (eg sms message) when I want it
  3) When the Today scope reloads, not only is it slow (BQ 4.5) but it also takes down the entire scope system with it for a few seconds.

  The problem is that when the Today scope refreshes/reloads, it reloads
  all sub-scopes. However, Weather and Today do not need to be reloaded
  for 24 hours at a time (maybe weather is an exception here).

  I think the Today scope should be a 'dumb placeholder' and the sub-
  scopes should be responsible for calling for refresh. The parent
  (Today scope) could then refresh an _individual_ sub-scope using ajax
  or similar. This would improve all three issues above but challenge
  some other fundamentals, eg:

  4) Scopes should be stateless (according to current thinking)

  I would challenge this also, as it would solve the issue where the My
  Music scope shows the user their music sorted by artist, even after
  they have changed it to album sorting.

  The Today scope has come a long way since I got the phone in April and
  I now have it enable since the latest update a few weeks ago. But the
  issues I describe above are 'as expected' behaviour and I think this
  itself is the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1500467/+subscriptions