Confirmed users
169
edits
Services/F1/Design: Difference between revisions
Jump to navigation
Jump to search
→Outline of F1 Design
Mixedpuppy (talk | contribs) |
Mixedpuppy (talk | contribs) |
||
| Line 33: | Line 33: | ||
10. The Python server will only store temporary state via session management that is required during the openid and oauth authorization. No state is stored for the contacts or send api calls. The temporary state is stored in membase. | 10. The Python server will only store temporary state via session management that is required during the openid and oauth authorization. No state is stored for the contacts or send api calls. The temporary state is stored in membase. | ||
11. The oauth workers (really a part of the python server for now) may send status information into Membase for use by the status service. This information is basically about the health of the 3rd party service (e.g. x failures in the past x minutes). | 11. The oauth workers (really a part of the python server for now) may send status information into Membase for use by the status service. This information is basically about the health of the 3rd party service (e.g. x failures in the past x minutes). I've separated them into their own box as they are in their own python module on github at mozilla/server-share-core. | ||
12. Assume that any data sent to the api in #8 is also sent to the 3rd party. Likewise, any data returned will be returned to the client. | 12. Assume that any data sent to the api in #8 is also sent to the 3rd party. Likewise, any data returned will be returned to the client. | ||