This queue is for tickets about the Net-Telnet CPAN distribution.

Report information
The Basics
Id:
101506
Status:
rejected
Priority:
Low/Low
Queue:

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

BugTracker
Severity:
Wishlist
Broken in:
(no value)
Fixed in:
(no value)



Subject: Async / AnyEvent Support
How hard would it be to have full async support (connecting, disconnecting, issuing commands, retrieving data, etc.) and then have an AnyEvent-aware wrapper, probably AnyEvent::Telnet which is similar to how AnyEvent::SNMP and others work? I took a look at some of the other AnyEvent libs and I have no idea where to begin to port this to be AnyEvent capable or else I'd try doing it myself :)
Sorry it has taken so long to get back to you. I am not familiar with AnyEvent. I think it is outside the realm of Net::Telnet to add some type of event driven code. Note that a Net::Telnet object is a subclass of IO::Socket::INET. You could use select() to see if there is something to read and use Net::Telnet::buffer() if there is something already read but not returned via the API. On Mon Jan 12 14:32:25 2015, DEFCON wrote:
Show quoted text
> How hard would it be to have full async support (connecting, > disconnecting, issuing commands, retrieving data, etc.) and then have > an AnyEvent-aware wrapper, probably AnyEvent::Telnet which is similar > to how AnyEvent::SNMP and others work? I took a look at some of the > other AnyEvent libs and I have no idea where to begin to port this to > be AnyEvent capable or else I'd try doing it myself :)


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

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