[nama] Re: JSON: (was Re: Re: Singleton branch passes all tests)
- From: "S. Massy" <lists@xxxxxxxxxxxx>
- To: nama@xxxxxxxxxxxxx
- Date: Fri, 16 Sep 2011 12:22:17 -0400
On Wed, Sep 14, 2011 at 01:59:06AM -1000, Joel Roth wrote:
> A lot of good stuff happened today. Basically, I decided
> to make the serialization more flexible. However,
> I may be doing some overkill.
>
> If you have State files in multiple formats, (i.e.
> State.yml, State.json, State.pl) Nama will load the newest.
>
> I'll be doing that with other effect_chains and
> effect_profiles, too. That way a newly written
> effect_chain.pl files will not clobber an existing
> effect_chain.yml files and will get loaded preferentially.
>
> I'm considering giving the user a choice of
> formats via a new namarc setting:
>
> serialization:
> - yaml
> - perl
>
> This tells Nama to write both State.yml and State.pl.
> The latter will be created later, so when
> loading it will be the default source.
>
> However if the user happens to edit State.yml,
> the change in date-modified will signal Nama
> to load it preferentially.
>
> You'll have a backup copy of your settings in
> State.pl, in case you happen to botch your
> editing of State.yml.
>
> For simpler behavior, a single serialization
> setting will do.
This is great for backward compatibility and testbed purposes, but
doesn't it complicate your job, or is enough of the code for various
formats shared that it matters little?
Cheers,
S.M.
Other related posts:
