Skip Menu |
 

This queue is for tickets about the Message-Passing CPAN distribution.

Report information
The Basics
Id: 99471
Status: open
Priority: 0/
Queue: Message-Passing

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: IO::Async instead of AnyEvent?
Download (untitled) / with headers
text/plain 185b
Is there any appetite for converting from using AnyEvent in the backend to IO::Async? AnyEvent is problematic because of its lack of license, as well as various implementation details.
Download (untitled) / with headers
text/plain 109b
Definitely from my side after I was in contact with the author of AnyEvent because of another of his modules.
Download (untitled) / with headers
text/plain 267b
I looked into it and I'm not sure if we can pull this of because not only Message::Passing itself but all the components use AnyEvent. Is it possible to mix IO::Async with AnyEvent to both modules can be used together and each author can choose his/her preferred one?


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.