946
edits
Firefox/Projects/AccountManager/Meetup/Analysis: Difference between revisions
Jump to navigation
Jump to search
Firefox/Projects/AccountManager/Meetup/Analysis (view source)
Revision as of 22:08, 4 June 2010
, 4 June 2010→Rejected Ideas
(Created page with 'Key take-aways distilled from the notes; changes we plan to make to the spec based on discussions during the meetup: = Key Proposals = ;Static resolution of multiple AMCDs per-…') |
|||
| Line 25: | Line 25: | ||
= Rejected Ideas = | = Rejected Ideas = | ||
;JS API for setting status | |||
This goes hand-in-hand with in-content markup for setting the status. While we aren't completely opposed to the idea, we are trying to avoid that in order to completely side-step any XSS attacks. | This goes hand-in-hand with in-content markup for setting the status. While we aren't completely opposed to the idea, we are trying to avoid that in order to completely side-step any XSS attacks. | ||
;JSON in headers | |||
Sadly, JSON isn't 7-bit clean, which headers need to be. We would need to Base-64 encode the header, which would be a lot worse to look at (though relatively easy to implement). Maybe someday... | Sadly, JSON isn't 7-bit clean, which headers need to be. We would need to Base-64 encode the header, which would be a lot worse to look at (though relatively easy to implement). Maybe someday... | ||
;Multiple IDs in the status header | |||
We're not sold on this. We think those are probably multiple realms, and should be represented as multiple AMCDs. | We're not sold on this. We think those are probably multiple realms, and should be represented as multiple AMCDs. | ||