Doco: interaction overview

[GoogleCodeExporter]

We have wiki post Interaction_Overview, which is outdated.

We need a new post that explains how M. talks to ZP. Better use a sequence
of UML diagrams and maybe one line of text to explain what a diagram is about.

1. The high level overview from the moment a user hits a page.
So, what happens?
We probably check user creds.
Then we get template details.
Generate a form, etc, etc.
Just the high level steps, but need to be all of them. From the beginning
to the end when an order was paid and files generated.
It will be a busy diagram, so keep the steps high level.

2. Steps that are of interest, e.g. user registration, order generation,
etc, etc, need to have their own diagrams with details what calls what,
where data is stored, if any, what API is used, and so on.

These daigrams will be a blueprint of the integration process. A programmer
would look at them and get a clear idea how it all works. Not everyone has
time to dig through the code.

Original issue reported on code.google.com by zetapri...@gmail.com on 15 Mar 2010 at 11:04

[GoogleCodeExporter]

See Interaction_overview for diagrams

Original comment by Anatoly....@gmail.com on 29 Mar 2010 at 4:49

• Changed state: ToTest

[GoogleCodeExporter]

Original comment by zetapri...@gmail.com on 30 Mar 2010 at 10:13

• Changed state: Done