view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    serialise/deserialise them.

FAQs

 Why not ZeroMQ?

    I found ZeroMQ to be a lot of effort to use from Perl, and most
    critically it does not appear to support both request/response and
    publish/subscribe message flows to share the same UNIX socket. To
    support that in ZeroMQ it would appear to be necessary to create two
    separate endpoints, one for each kind of message flow.

 Why not JSON/YAML/your-favourite-serialisation?

    I mostly built this for a few very-small use-cases involving simple
    byte strings or plain ASCII text, for which the overhead of JSON, YAML,
    or other kinds of serialisation would be unnecessary. As the presented
    message semantics are just opaque byte buffers, you are free to layer
    on top whatever kind of message serialisation you wish.

 Why not IO::Async/Mojo/your-favourite-event-system?

lib/IPC/MicroSocket.pm  view on Meta::CPAN

   }
}

=head1 FAQs

=head2 Why not ZeroMQ?

I found ZeroMQ to be a lot of effort to use from Perl, and most critically it
does not appear to support both request/response and publish/subscribe message
flows to share the same UNIX socket. To support that in ZeroMQ it would appear
to be necessary to create two separate endpoints, one for each kind of message
flow.

=head2 Why not JSON/YAML/your-favourite-serialisation?

I mostly built this for a few very-small use-cases involving simple byte
strings or plain ASCII text, for which the overhead of JSON, YAML, or other
kinds of serialisation would be unnecessary. As the presented message
semantics are just opaque byte buffers, you are free to layer on top whatever
kind of message serialisation you wish.