Skip Menu |
 
Update: The rt.cpan.org bug tracker service is no longer shutting down.

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

Report information
The Basics
Id: 101506
Status: rejected
Priority: 0/
Queue: Net-Telnet

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

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



Subject: Async / AnyEvent Support
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-30342-1421091144-1874.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 394
Download (untitled) / with headers
text/plain 394b
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 :)
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-30342-1421091144-1874.0-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-30342-1421091144-1874.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-16230-1582066194-1840.101506-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 845
Download (untitled) / with headers
text/plain 845b
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 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.