[DOC] Documentation on data-request-flow
Reported by MS | January 6th, 2009 @ 08:17 AM
I would like to know more about how the information flows inside and outside nitrogen:
- inside nitrogen: which module calls which one to do what
- outside nitrogen:
- what kind of requests are there (Page-Rendering, Comet, etc.)
- how are these submitted (POST, GET, including especially their parameters, name of the parameters, etc.)
so we can ultimately draw some nice "information flow diagrams".
These diagrams might become quite usefull for the other open tasks like the problem wrt make_ref(), how encoded and what we store in cookies, what gets serialized in the java scripts, etc.
Comments and changes to this ticket
-
MS January 6th, 2009 @ 08:20 AM
The "inside nitrogen: [...]" stuff is missing some important information. I think it would be enough to know, what each module's task is, and how the modules interact:
- wf_handle
- Tasks
- handle requests coming from different web-servers,
- setup process state for request processing
- calls
- wf_state
- ...
- Tasks
- wf_state
- Tasks
- store state related to a page rendering process
- serialize / deserialize page state from a POST request
- supports dump / restore for distributed rendering
- Tasks
- wf_handle
-
Rusty Klophaus June 14th, 2010 @ 06:41 PM
- Milestone set to “2.0.2”
-
Rusty Klophaus June 29th, 2010 @ 08:00 PM
- Milestone cleared.
- Milestone order changed from “0” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Nitrogen Web Framework for Erlang
MS
Rusty Klophaus