| Name : perl-POE-Component-IRC
| |
| Version : 6.90
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.1
| Date : 2017-10-04 18:04:36
|
| Group : Development/Libraries/Perl
| Source RPM : perl-POE-Component-IRC-6.90-1.1.src.rpm
|
| Size : 1.12 MB
| |
| Packager : (none)
| |
| Summary : Fully event-driven IRC client module
|
Description :
POE::Component::IRC is a POE component (who\'d have guessed?) which acts as
an easily controllable IRC client for your other POE components and
sessions. You create an IRC component and tell it what events your session
cares about and where to connect to, and it sends back interesting IRC
events when they happen. You make the client do things by sending it
events. That\'s all there is to it. Cool, no?
[Note that using this module requires some familiarity with the details of
the IRC protocol. I\'d advise you to read up on the gory details of RFC 1459
(http://www.faqs.org/rfcs/rfc1459.html) before you get started. Keep the
list of server numeric codes handy while you program. Needless to say,
you\'ll also need a good working knowledge of POE, or this document will be
of very little use to you.]
The POE::Component::IRC distribution has a _docs/_ folder with a collection
of salient documentation including the pertinent RFCs.
POE::Component::IRC consists of a POE::Session that manages the IRC
connection and dispatches \'irc_\' prefixed events to interested sessions and
an object that can be used to access additional information using methods.
Sessions register their interest in receiving \'irc_\' events by sending
\'register\' to the component. One would usually do this in your \'_start\'
handler. Your session will continue to receive events until you
\'unregister\'. The component will continue to stay around until you tell it
not to with \'shutdown\'.
The SYNOPSIS demonstrates a fairly basic bot.
See POE::Component::IRC::Cookbook for more examples.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/openSUSE_Leap_42.2/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
perl(POE::Component::IRC)
perl(POE::Component::IRC::Common)
perl(POE::Component::IRC::Constants)
perl(POE::Component::IRC::Plugin)
perl(POE::Component::IRC::Plugin::AutoJoin)
perl(POE::Component::IRC::Plugin::BotAddressed)
perl(POE::Component::IRC::Plugin::BotCommand)
perl(POE::Component::IRC::Plugin::BotTraffic)
perl(POE::Component::IRC::Plugin::CTCP)
perl(POE::Component::IRC::Plugin::Connector)
perl(POE::Component::IRC::Plugin::Console)
perl(POE::Component::IRC::Plugin::CycleEmpty)
perl(POE::Component::IRC::Plugin::DCC)
perl(POE::Component::IRC::Plugin::FollowTail)
perl(POE::Component::IRC::Plugin::ISupport)
perl(POE::Component::IRC::Plugin::Logger)
perl(POE::Component::IRC::Plugin::NickReclaim)
perl(POE::Component::IRC::Plugin::NickServID)
perl(POE::Component::IRC::Plugin::PlugMan)
perl(POE::Component::IRC::Plugin::Proxy)
perl(POE::Component::IRC::Plugin::Whois)
perl(POE::Component::IRC::Qnet)
perl(POE::Component::IRC::Qnet::State)
perl(POE::Component::IRC::State)
perl(POE::Filter::IRC)
perl(POE::Filter::IRC::Compat)
perl-POE-Component-IRC
Requires :
