CPAN::Groonga

e Event::RPC::Message::JSON;

use base Event::RPC::Message::SerialiserBase;

use strict;
use utf8;

use JSON::XS 3.0;

my $decoder = JSON::XS->new->allow_tags;
my $encoder = JSON::XS->new->latin1->all

ge::JSON - JSON message formatting

=head1 SYNOPSIS

  # Internal module. No documented public interface.

=head1 DESCRIPTION

This module implements the message formatting of Event::RPC
using JSON. O

 public interface.

=head1 DESCRIPTION

This module implements universal FREEZE/THAW methodes
for JSON and CBOR based message format classes. Unfortunately
these modules can't take callbacks for these

ules => 1,
      connection_hook     => sub { ... },

      message_formats     => [qw/ SERL CBOR JSON STOR /],
      insecure_msg_fmt_ok => 1,
  );

  $server->set_max_packet_size(2*1024*1024*1024);

amed "message formats" here:

  SERL -- Sereal::Encoder, Sereal::Decoder
  CBOR -- CBOR::XS
  JSON -- JSON::XS
  STOR -- Storable

Server and client negotiate automatically which format is
best to use

amed "message formats" here:

  SERL -- Sereal::Encoder, Sereal::Decoder
  CBOR -- CBOR::XS
  JSON -- JSON::XS
  STOR -- Storable

Server and client negotiate automatically which format is
best to use

o use Storable in real world szenarios. Better
use one of the other alternatives (Sereal, CBOR or JSON).

=head1 AUTHORS

  Jörn Reder <joern at zyn dot de>

=head1 COPYRIGHT AND LICENSE

Copyright (

vent::RPC::Message::CBOR",
    "JSON"  => "Event::RPC::Message::JSON",
    "STOR"  => "Event::RPC::Message::Storable",
);

my @MESSAGE_FORMAT_ORDER = qw( SERL CBOR JSON STOR );

sub known_message_form

of the following modules for
data serialisation:

  Sereal (::Decoder and ::Encoder)
  CBOR::XS
  JSON::XS
  Storable

Server and client negotiate automatically which serialiser to use
to achieve maxi