*If* it's possible for the shell to return "unknown", then yes I think the shell should be initializing the session per the example. That said, as I didn't write the code, and have zero direct experience with QNetworkAccessManager. I was just pointing out that this was suggested as a way to prevent "unknown" from ever being returned.
Anyways, it seems like there's not really anything more that I can contribute from a networking stack developer's perspective, so I'll abstain from further comments for now...
@Michi
Hmmm, I expected lp to auto-link "comment #7" to the comment in this bug, but that apparently didn't work:
https:/ /bugs.launchpad .net/ubuntu/ +source/ unity-scopes- api/+bug/ 1502282/ comments/ 7
*If* it's possible for the shell to return "unknown", then yes I think the shell should be initializing the session per the example. That said, as I didn't write the code, and have zero direct experience with QNetworkAccessM anager. I was just pointing out that this was suggested as a way to prevent "unknown" from ever being returned.
Anyways, it seems like there's not really anything more that I can contribute from a networking stack developer's perspective, so I'll abstain from further comments for now...