in reply to Waiting for callback event

AIM bots have to be programmed in an event driven style. Well they don't HAVE to be, but it makes life easier.

This means that you need to break that sequence of commands you have down, and put them in the events when they should be executed. As was already mentioned you need to use do_one_loop to tell the AIM protocol you are ready for it to loop, then keep calling do_one_loop constantly, normaly in an infinite loop of sorts.

If you would like to learn more about bot programming you can check out my forums at http://Bot-depot.com, there are programmers there of all levels of experience. Many of us program AIM,MSN, Jabber and IRC bots in perl, and there are some who use other languages like VB and PHP. Good luck.


___________
Eric Hodges

Replies are listed 'Best First'.
Re^2: Waiting for callback event
by cow4263 (Initiate) on Nov 22, 2004 at 19:57 UTC
    As I may have mentioned in the hastily written reply above, I would like these events to occur before the infinite do_once_loop() (or as I like to refer to it, interactive mode). I have a feeling that manually calling do_once_loop() will get the results I desire, but that will have to wait until I get home later tonight.
[reply]

      I beleive that you can add multiple buddies, and then commit the list. Other than that I would setup a que of buddies to add, add one, and then add another and commit everytime you get the buddylist_ok() or buddylist_error().

      Calling do_one_loop manualy between each call will be iffy at best. Its going to go check each socket and see if there is something new. If there is no message then it returns, if there is then it processes it and calls the event. You would be counting on your events to come at the right time and in the right order, which is generaly a bad idea. I think you should probably focus more on how to fit your needs into an event driven program.


      ___________
      Eric Hodges
[reply]

In Section Seekers of Perl Wisdom