On a tiny keyboard... But one thing - the use tested mocks are very webby in feel, and we already have an initial HTML implementation...
And for scope of responsibility, was thinking initially, if user is not signed in, open container, and it returns email, some auth keys, etc. Pretty narrow scope is my first guess, all persistence in chrome... Lloyd Nick Alexander <[email protected]> wrote: On 13-08-09 7:31 AM, Lloyd Hilaiel wrote: > Chris Karlof and I were talking yesterday, and I was noting how awesome the > implementation approach of Persona on FirefoxOS has been. The, the relevant > code that ships with the device is limited to a container capable of running > web content, and some setup code which invokes a function within the context > of that web content when necessary. Further, the navigator.id. apis are > intercepted by firefoxos, and cause raising of the "trusted" content window > and relaying parameters into it. <snip> > Is there any really good reason not to explore this option? Technical question. IIUC, the Persona shim stores private user details in localStorage (and in persona.org cookies). What happens when the user clears local data? It's my belief that Persona just expects you to re-authenticate to the email address you entered. If my understanding is correct, we'll need to be more durable than that: we can't forget the user's account and we can't expect re-auth. So that means the UI shim can't be authoritative for this data. Nick _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
