Yet Another CPAN Grep

Log-Message-JSON ( D/DO/DOZZIE/Log-Message-JSON-0.03.tar.gz, DOZZIE, 2012; MetaCPAN )

Log-Message-JSON/lib/Log/Message/JSON.pm ( view source; MetaCPAN )

head1 NAME

Log::Message::JSON - structured messages that stringify to JSON

=head1 SYNOPSIS

  package My::Application::Module;

  use Log::Log4perl;
  use Log::Message::JSON qw{logmsg};

  sub do_so

, which
appenders could be in use and defeats much of Log::Log4perl's flexibility.

Log::Message::JSON is an attempt to solve this problem. Developer can create
a message that has an internal structur

f)), and at the
same time it can be used as a simple string, instantly serializing to
single-line JSON. This way the developer don't need to decide on appenders in
advance. Moreover, flat string logfi

Log-Message-JSON ( D/DO/DOZZIE/Log-Message-JSON-0.03.tar.gz, DOZZIE, 2012; MetaCPAN )

Log-Message-JSON/lib/Log/Message/JSON/Hash.pm ( view source; MetaCPAN )

AME

Log::Message::JSON::Hash - L<Tie::IxHash(3)> wrapper supporting storing cache

=head1 SYNOPSIS

  use Log::Message::JSON::Hash;
  use JSON;

  tie my %hash, "Log::Message::JSON::Hash";
  # fill %

hash...
  tied(%hash)->cache = encode_json(\%hash);

  # ...

  print tied(%hash)->cache;

=head1 DESCRIPTION

This class is a proxy to L<Tie::IxHash(3)>. It's a valid class to tie hash to,
and above

--------------------------------------------------------------------------

package Log::Message::JSON::Hash;

use warnings;
use strict;

use Tie::IxHash;
use Carp;

#---------------------------------