machi/src/machi.app.src

{application, machi, [
    {description, "A village of write-once files."},
    {vsn, "0.0.0"},
    {applications, [kernel, stdlib, crypto]},
    {mod,{machi_app,[]}},
    {registered, []},
    {env, [
           {flu_list,
            [
             %%%%%% {flu_a, 32900, "./data.flu_a"}
            ]}
    ]}
]}.
Single server client & server code (squashed) 2015-03-31 07:46:03 +00:00			`{application, machi, [`
			`{description, "A village of write-once files."},`
			`{vsn, "0.0.0"},`
Hooray, PULSE things look stable; remove debugging verbose cruft 2015-07-16 12:57:34 +00:00			`{applications, [kernel, stdlib, crypto]},`
Single server client & server code (squashed) 2015-03-31 07:46:03 +00:00			`{mod,{machi_app,[]}},`
			`{registered, []},`
			`{env, [`
			`{flu_list,`
			`[`
Add machi_flu_psup.erl to supervise all 3 FLU processes (see below) Introduce machi_flu_psup:start_flu_package/4 as a way to start all related FLU processes * The projection store * The chain manager * The FLU itself ... as well as linked processes. http://www.snookles.com/scotttmp/flu-tree-20150430.png shows one FLU running, "a". The process registered "a" is the append server, "some-prefix" for the sequencer & writer for the current <<"some-prefix">> file, and a process each for 3 active TCP connections to that FLU. 2015-04-30 08:28:43 +00:00			`%%%%%% {flu_a, 32900, "./data.flu_a"}`
Single server client & server code (squashed) 2015-03-31 07:46:03 +00:00			`]}`
			`]}`
			`]}.`