root/mirror/edenwall/nulog2/branches/2.0/doc/sessions.rst

Revision 8112, 1.1 kB (checked in by haypo, 3 years ago)
  • Use RST section-numbering
  • intro.rst: list all other documentations
  • move vocabulary.rst text into intro.rst
  • Property svn:mime-type set to text/x-rst; charset=utf8

NuLog sessions

This file will describe how NuLog2 store user parameters into persistant sessions.

1   Architecture

Because we save datas into files, we must formalize them with some key/value lines.

A key is formated like this:

<type>.<ID>[.<attr>]

We will call object the entity which type type and named ID.

First, all keys are prefixed with his kind of object:

page.<ID>.<attr>:       Page
frag.<ID>.<attr>:       Fragment

An object

1.1   Pages

Each page we want to store paramters will have a tuple in this syntax:

page.<pagename>.frags = <fragID1>[ <fragID2> ...]

A page have an uniq ID which is his name in nulog-web.

1.2   Fragments

A fragment jave an uniq ID which is in this form:

<page>_<function>[<number>]

This is a convention and it isn't important, but will be respected by Nulog.

This is all attributs of a frag object:

frag.<ID>.function   : function name
frag.<ID>.arg.<arg>   : arg is an argument name, and value of this tuple is argument value.
Note: See TracBrowser for help on using the browser.