On Mon, Dec 22, 2014 at 12:27 PM, Shane Tomlinson <[email protected]> wrote: > As I sent this, a PR came in for the PyFxA client - the Python relier > library [1]. >
Yes indeed :) I just submitted some code I had in a proof-of-concept API. I totally agree on the clients consistency. I found myself hesitating : trade token ? trade code ? verify ? verify token ? Naming methods can sometimes be matter of taste, and it's quite easy to diverge :) > Shane > > ============ > > [1] - https://github.com/mozilla/PyFxA > > On Mon, Dec 22, 2014 at 11:25 AM, Shane Tomlinson <[email protected]> > wrote: >> >> Nick, I don't have any real desire for the client, I am just interested in >> its existence. Could this client be extracted from the firefox-ios repo if >> Mozilla ever decides to write another iOS app? >> >> > I expect another small library to consume the FxA client account state >> > and to handle the token server interactions. >> >> Zach Carter wrote two JS clients and Ryan Kelly is working on a Python >> client to handle this. Perhaps there is an opportunity to present a >> consistent(ish) API across the languages? >> >> Zach's JS clients are embedded in the fxa-content-server [1][2]; I'd like >> to extract them into the fxa-relier-client [3] so the functionality is >> available to any JS based relier. I'm not sure where Ryan's repo is located, >> my Github search foo did not find anything obvious. >> >> Shane >> >> ================== >> >> [1] - >> https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/oauth-client.js >> [2] - >> https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/profile-client.js >> [3] - https://github.com/mozilla/fxa-relier-client >> >> >> On Wed, Dec 17, 2014 at 5:23 PM, Nicholas Alexander >> <[email protected]> wrote: >>> >>> Hey! >>> >>> On Wed, Dec 17, 2014 at 8:46 AM, Shane Tomlinson <[email protected]> >>> wrote: >>>> >>>> I opened up the firefox-ios repo today and was delighted to see the >>>> directories FxA and FxAClient. In FxAClient, there is a file called >>>> FxAClient.swift[1], written by rnewman. Who consumes this client, is it >>>> only >>>> the browser? >>> >>> >>> At the moment, only the browser, and not even that yet. We're hoping to >>> keep the FxA client pretty thin -- no connection to the browser, no >>> connection to Sync. >>> >>> My current vision for the FxA client is for it to maintain an abstraction >>> of the Account State (equivalent to Desktop's `signedInUser.json`) and for >>> it to handle the HTTP calls to advance that state through a login state >>> machine. I have a PR in progress for this work; hopefully I can post by >>> EOW. >>> >>> I expect another small library to consume the FxA client account state >>> and to handle the token server interactions. >>> >>> It's not yet clear to me if the FxA client will handle the UI for signing >>> up and/or in. >>> >>> What's your desire for this client? >>> >>> Nick >>> >>>> >>>> >>>> Shane >>>> >>>> ======= >>>> >>>> [1] - >>>> https://github.com/mozilla/firefox-ios/blob/master/FxAClient/FxAClient.swift >>>> >>>> _______________________________________________ >>>> Dev-fxacct mailing list >>>> [email protected] >>>> https://mail.mozilla.org/listinfo/dev-fxacct >>>> >> > > > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct > _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
