This is going to be long, since I tried several things before posting.

X problem

The infamous CB<->IRC connection. My approach is different, though:

Y problem

When I send a message to myself on the IRC server, of course a PRIVMSG event is dispatched (the event is exactly called ircd_client_privmsg). There's a function taking care of this (ircd_client_message) but I need to additionally run some own code in order to send the message to PM. The key is: seemingly you cannot tell PoCo::Server::IRC "Hey!, warn me whenever that event occurs!".

Base code

This is the base code I'm playing with. It's virtually identical to the code supplied in the documentation:

#!/usr/bin/perl
 
use warnings;
use strict;
use POE;
use POE::Component::Server::IRC;

my $pocosi = POE::Component::Server::IRC->spawn (Alias => 'ircd', Debu
+g => 1);

POE::Session->create (
    inline_states => {
        _start => \&test_start,
        _stop  => \&test_stop, 
    },
    heap => { Obj  => $pocosi },
);
$poe_kernel->run();
exit 0;

sub test_start {
    my ($kernel,$heap) = @_[KERNEL,HEAP];

    $kernel->post ( 'ircd' => 'register' );
    $kernel->post ( 'ircd' => 'configure' => { Auth => 1, AntiFlood =>
+ 1 } );
    $kernel->post ( 'ircd' => 'add_i_line' => { IPMask => '*', Port =>
+ 6667 } );
    $kernel->post ( 'ircd' => 'add_operator' => { UserName => 'Flibble
+', Password => 'letmein' } );
    $kernel->post ( 'ircd' => 'add_listener' => { Port => 6667 } );
    $kernel->post ( 'ircd' => 'set_motd' => [ 'This is an experimental
+ server', 'Testing POE::Component::Server::IRC', 'Enjoy!' ] );
}
 
sub test_stop {
    print "Server stopped\n";
}
[download]

First attempt

The first things I tried were related to the way the POE::Session was being created:

POE::Session->create (
    inline_states => {
        _start => \&test_start,
        _stop  => \&test_stop, 
#       ircd_client_privmsg => \&POE::Component::Server::IRC::hue_priv
+msg_handler,                           ## 1
    },
#   object_states => [ $pocosi => { ircd_client_privmsg => 'hue_privms
+g_handler' },],                        ## 2
#   package_states => [ 'POE::Component::Server::IRC' => { ircd_client
+_privmsg => 'hue_privmsg_handler' },], ## 3
    heap => { Obj  => $pocosi },
);
[download]

I played with every one of those commented lines without success. I created the sub in the package POE::Component::Server::IRC and not in main because that's the way #2 works, and it does no harm to the rest of the module. It never gets called. But if I add this to test_start:

$kernel->post ( 'ircd', 'ircd_client_privmsg', 'test1');
$kernel->delay ( 'ircd_client_privmsg', 2, 'test2');
[download]

Then my code finally runs one time. It doesn't matter which of the three approaches I try, it works with all. The function gets the parameter 'test2'. If I turn on POE::Kernel tracing (using sub POE::Kernel::TRACE_DEFAULT() {1} as documented) I can see that that event is dispatched to session 5, while all other events go to session 2. Session 5 is the one I'm playing with, session 2 is created inside the module code. This does not help, because I can't get the session 2's ID.

Second attempt

Let's remove the $kernel->delay line and the three ones added to the session constructor, leaving only the $kernel->post one, since this sends events to the session that matters. Next plan deals with overriding POE::Component::Server::IRC::ircd_client_message with my own function, and then call the original from there. Tried this:

my $pocosi_ircd_client_message = \&POE::Component::Server::IRC::ircd_c
+lient_message;
sub POE::Component::Server::IRC::ircd_client_message {
    print "got in!\n";
#   $pocosi_ircd_client_message->(@_);
}
[download]

This way my code runs. Then I uncomment the line that calls the original sub and surprise! It's my sub which is called again, in an infinite fashion :). Of course, when I redefine the function, I don't get a copy so $pocosi_ircd_client_message keeps "pointing" to the same place. The original function is lost. If I could take a copy of it, that would be resolved.

So...

Well, I'm stuck with this. Maybe the solution has to do with implementing that kind of "Hey!" messages I talked about at the beginning. Or maybe I could subclass the module and define my own spawn method, which I could take the ID of, and play with that solution I mentioned earlier. Or maybe... ideas welcome!