Skip to content

API Unification #29

Description

@chloe-zen

The differences between zmq2 and zmq3 could be effectively papered over by providing a superset of the APIs down at the ZMQ level. For example, sendmsg and recvmsg can easily be made to work on ZMQ::Socket using both underlying libraries.

Are you open to this kind of change?

Also, error reporting would be Much Nicer if either $! integration were more advanced or zmq_strerror was exposed via the base ZMQ. Or both.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions