Net::AIM - raising the white flag

djberg96 on 2003-03-07T15:36:00

Yesterday I officially raised the white flag on the Net::AIM port and sent out a request for help on the Ruby developer's mailing list.

For some reason it's choking on the recvfrom calls and I haven't a clue why. To make matters worse, at home it dies in a different place than it does at work, and running under the debugger seems to cause errors that don't happen otherwise.

Argh...


Have you tried Net::AIMTOC?

dmarner on 2003-03-10T12:44:42

I am using it in a program that sends caller-id info from my modem to wherever I am logged on to AIM. I am only using it to send messages, not receive, so I can't attest that the whole API works.

Another plus to Net::AIMTOC is that it is using TOC rather than OSCAR. In theory, AOL doesn't change TOC to break non-AIM clients like they do OSCAR.

I tried Net::AIM first, too, and gave up.

Re:Have you tried Net::AIMTOC?

djberg96 on 2003-03-11T17:38:05

Hmm...I'm having even less luck with Net::AIMTOC than I am with Net::AIM. The latter would at least let me login, though sending messages didn't seem to work. Net::AIMTOC doesn't even get that far for me.

Re:Have you tried Net::AIMTOC?

dmarner on 2003-03-11T18:16:05

This code works for me, using Net::AIMTOC v0.94 and perl 5.8.0 as shipped with Mandrake 9.

use Net::AIMTOC;

my $aim = Net::AIMTOC->new;
$aim->connect;
$aim->sign_on( 'brringbot', 'password' );
$aim->send_im_to_aol( 'paxsdad', 'this is an example message');