[Sputnik-list] Patch: NOCREATE flag on node_defaults

[Jim Whitehead II]

On 3/5/08, pierre pracht <pierre.pracht at gmail.com> wrote:
>
>  Le 5 mars 08 à 11:56, Jim Whitehead II a écrit :
>
>
>  > I've submitted the following ticket
>  > (http://sputnik.freewisdom.org/en/Ticket:000018) that allows for a
>  > NOCREATE flag on any node_default.  This flag would stop the page from
>  > being saved in the versium repository when pulled as a node default.
>
>
> When versium would be brake in part, it would be more simple.
>  I have made some test code
>
>  repo.versium = versium.open{
>         storage = "versium.storage.simple_compose",
>         params = {
>            params_write_store = {
>               storage = "versium.storage.simple",
>               params = initial_config.VERSIUM_PARAMS,
>            },
>            params_default_store = {
>               storage = "versium.storage.simple_node_defaults",
>               params = {base_module="sputnik.node_defaults."},
>            }
>         }
>     }
>
>  versium.storage.simple_node_defaults : read default node (from modules)
>  versium.storage.simple : not changed
>  versium.storage.simple_compose : compose two storage
>    - first : read-write
>    - second : read-only
>  When a node is read, it is take from first if present. If not it is
>  read from second.
>  When a node is write, it is write to first.
>
>
>  > but in a development environment it makes testing and
>  > deploying new default files rather difficult.

How and when is the versium split happening and who is primarily
working on it?  I have a few suggestions and ideas that I've brought
up in other threads, and would be open to more in-depth discussion
about them.

- Jim