App-Config-Chronicle

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN


 chronicle_writer

    The chronicle store that updated configurations can be stored into it.
    It should be an instance of Data::Chronicle::Writer. But user is free
    to implement any storage backend he wants if it is implemented with a
    'set' method.

 chronicle_subscriber

    The chronicle connection that can notify via callbacks when particular
    configuration items have a new value set. It should be an instance of
    Data::Chronicle::Subscriber.

 refresh_interval

    How much time (in seconds) should pass between check_for_update
    invocations until it actually will do (a bit heavy) lookup for settings
    in redis.

    Default value is 10 seconds

lib/App/Config/Chronicle.pm  view on Meta::CPAN


=cut

has chronicle_writer => (
    is  => 'rw',
    isa => 'Data::Chronicle::Writer',
);

=head2 chronicle_subscriber

The chronicle connection that can notify via callbacks when particular configuration items have a new value set. It should be an instance of L<Data::Chronicle::Subscriber>.

=cut

has chronicle_subscriber => (
    is  => 'ro',
    isa => 'Data::Chronicle::Subscriber'
);

has setting_namespace => (
    is      => 'ro',

lib/App/Config/Chronicle.pod  view on Meta::CPAN

The chronicle store that configurations can be fetch from it. It should be an instance of L<Data::Chronicle::Reader>.
But user is free to implement any storage backend he wants if it is implemented with a 'get' method.

=head2 chronicle_writer

The chronicle store that updated configurations can be stored into it. It should be an instance of L<Data::Chronicle::Writer>.
But user is free to implement any storage backend he wants if it is implemented with a 'set' method.

=head2 chronicle_subscriber

The chronicle connection that can notify via callbacks when particular configuration items have a new value set. It should be an instance of L<Data::Chronicle::Subscriber>.

=head2 refresh_interval

How much time (in seconds) should pass between L<check_for_update> invocations until
it actually will do (a bit heavy) lookup for settings in redis.

Default value is 10 seconds

=head2 check_for_update



( run in 0.377 second using v1.01-cache-2.11-cpan-8d75d55dd25 )