summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorFolker Bernitt <fbernitt@thoughtworks.com>2015-01-23 16:28:22 +0100
committerFolker Bernitt <fbernitt@thoughtworks.com>2015-01-23 16:28:22 +0100
commit562a35d2bf9fd0626f02f60a300a25dc9d9b055a (patch)
tree93c74a0cd7a541ae4a74b3f27466cd22e5e445d0 /doc
parent1cc036d2550a9f629e4b655596a86a6b44b027de (diff)
Added some info about the python backend.
- Issue #243
Diffstat (limited to 'doc')
-rw-r--r--doc/first-steps.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/first-steps.md b/doc/first-steps.md
index b2b059b0..14e11c1b 100644
--- a/doc/first-steps.md
+++ b/doc/first-steps.md
@@ -155,3 +155,18 @@ It references a color variable defined in \_colors.scss
Change the color value to something else. Then run the ./go build command again and refresh the page.
+## Next steps
+
+The pixelated user agent is based on the reactive (flightjs)[https://github.com/flightjs] framework and uses events as the primary way of control flow.
+
+## The life of mail.
+
+How does that list of mails get populated? We only had look onto the JavaScript side of things, there is also the Python side for the service. When we say service we mean a python application that delivers not only the resources for the web application but also provides a REST api to access and send mails.
+
+To give you a brief overview lets follow an email through the service.
+
+* Some javascript calls the MailsResource in service/pixelated/resources/mails_resource.py
+* The render_GET method asks the search engine for a list of matching mail ids. These mails are then request from the mail service.
+* The mail service asks the soledad querier.
+* The soledad querier fetches the mails from the soledad backend
+