> and had a question about backwards compatability for the desktop client. What
> I am looking at doing is changing the <title>Software purchase in
> progress</title> portion of the subscription_purchase_in_progress.html page to
> include the oath token and subscription id. This is so that a new api can be
> called with the subscription id to check the status directly and not be
> dependent on the js updating the title.
>
> So my question is will adding the oath token and subscription id to the title
> break the existing client? If so, do you have an alternate suggestion on how
> to pass back this info?
Hm, so adding the info is not a problem. However the client is
expecting "successful" that is either True or False. So this mechanism
will not work with the existing client, sorry for that.
We could add a new mechanism via the statusbar, webkit supports a
callback on statusbar changes. Or alternatively "console-message" that
is called when "A JavaScript console message was created.". This time
we need to build-in a version so that the client can simply ignore
message versions its does not understand :)
Let me know which one you pick so that I start testing, time is up
for natty unfortunately, we are behind feature/UI freeze.
On Wed, Mar 30, 2011 at 12:26:07PM -0500, Danny Tamez wrote:
> Hey!
Hi,
> I'm working on https:/ /bugs.launchpad .net/software- center- agent/+ bug/622732
Great!
> and had a question about backwards compatability for the desktop client. What purchase_ in_progress. html page to
> I am looking at doing is changing the <title>Software purchase in
> progress</title> portion of the subscription_
> include the oath token and subscription id. This is so that a new api can be
> called with the subscription id to check the status directly and not be
> dependent on the js updating the title.
>
> So my question is will adding the oath token and subscription id to the title
> break the existing client? If so, do you have an alternate suggestion on how
> to pass back this info?
Hm, so adding the info is not a problem. However the client is
expecting "successful" that is either True or False. So this mechanism
will not work with the existing client, sorry for that.
We could add a new mechanism via the statusbar, webkit supports a
callback on statusbar changes. Or alternatively "console-message" that
is called when "A JavaScript console message was created.". This time
we need to build-in a version so that the client can simply ignore
message versions its does not understand :)
Let me know which one you pick so that I start testing, time is up
for natty unfortunately, we are behind feature/UI freeze.
Cheers,
Michael