touch-packages team mailing list archive

[Launchpad Bug Tracker <1359177@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity-scopes-api -
0.6.5+14.10.20140910.1-0ubuntu1

---------------
unity-scopes-api (0.6.5+14.10.20140910.1-0ubuntu1) utopic; urgency=medium

  [ Pawel Stolowski ]
  * Added support for expandable widgets.
  * Enhanced ActionMetadata with hints, similar to SearchMetadata. (LP: #1308585)
  * Push smart scopes online results immediately as they become available. (LP: #1359177)

  [ Michi Henning ]
  * Various fixes for race conditions and test stability.
    - This results in *safe* internal symbol changes.
  * Updates to scope tutorial and documentation.

  [ Ubuntu daily release ]
  * debian/libunity-scopes3.symbols: auto-update to released version
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Wed, 10 Sep 2014 08:49:56 +0000

** Changed in: unity-scopes-api (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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/1359177

Title:
  Showing results when available

Status in “unity-scopes-api” package in Ubuntu:
  Fix Released

Bug description:
  Sometimes, the server doesn't return the results immediately. In some
  cases, it even starts to send information, and keep producing it
  during time (because to produce the desirable set of results imply
  hitting the backend several times, which takes time).

  For example, the results delivery times may be:

    Result 0 (2855 msec)
    Result 1 (3339 msec)
    Result 2 (3343 msec)
    ...
    Result 9 (6871 msec)

  Currently, the client is waiting for everything to finish, and shows
  the whole page at once (with empty images, though, and after 7seconds,
  it starts to retrieve the images and show them).

  The ideal result is that the first result appear at 2.8s, the second
  at 3.3s, etc (and that the images start to be retrieved at *that*
  time).

  Pawel told in a mail that these results are handled by
  SmartScopesClient proxy in scopes middleware, and unfortunately it
  waits for all results before processing them and pushing them to the
  shell (via a "dummy" local smart scope).

  Marcus added that currently HttpClient is to request uri, and wait for
  the response. He should change the way QNetworkAccessManager is used
  to support this.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1359177/+subscriptions